Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759261AbaLKWhM (ORCPT ); Thu, 11 Dec 2014 17:37:12 -0500 Received: from v094114.home.net.pl ([79.96.170.134]:63150 "HELO v094114.home.net.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1759230AbaLKWhL (ORCPT ); Thu, 11 Dec 2014 17:37:11 -0500 From: "Rafael J. Wysocki" To: Linus Torvalds Cc: Tomi Valkeinen , Grant Likely , Rob Herring , "Rafael J. Wysocki" , LKML , Linux Fbdev development list , Mark Brown Subject: Re: [GIT PULL] fbdev fixes for 3.19 Date: Thu, 11 Dec 2014 23:58:42 +0100 Message-ID: <3272093.0A5V5UZ3cA@vostro.rjw.lan> User-Agent: KMail/4.11.5 (Linux/3.16.0-rc5+; KDE/4.11.5; x86_64; ; ) In-Reply-To: References: <54899F0E.4090309@ti.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="utf-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thursday, December 11, 2014 12:55:28 PM Linus Torvalds wrote: > On Thu, Dec 11, 2014 at 5:41 AM, Tomi Valkeinen wrote: > > > > Please pull fbdev changes for 3.19. > > Ugh. I've pulled it, but I'm not a huge fan of commit 6d09dc6b74ca > ("of.h: Keep extern declaration of of_* variables when !CONFIG_OF"). > > I guess it works, but it ends up delaying any failures from compile > time to link time, and the linker error messages likely won't be > great. > > So I'm cc'ing the OF people and Rafael (who worked on OF/ACPI > unification) to see if they have comments, preferences, or other ways > to solve this. > > Quite frankly, to me it smells like non-OF builds should just have an > empty "for_each_child_of_node ()" define instead of playing games with > externs that then end up not existing, and depending on the compiler > DTRT. > > Comments? "for_each_child_of_node ()" is not a problem here AFAICS, because in the example from the commit changelog the compiler would complain on the of_chosen instance in the "if ()" statement already anyway if I'm not mistaken. It wants all of the code in the given block to make sense even if that block will be optimized away going forward. That's not specific to CONFIG_OF too. I stumbled over that a couple of times and I don't see a clean and simple way to work around it at the moment. In the cases I dealt with it was sufficient to use static inlines that were defined to return NULL (or equivalent) when the symbol in question was not defined. Rafael -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/