[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201307041055.06561.arnd@arndb.de>
Date: Thu, 4 Jul 2013 10:55:06 +0200
From: Arnd Bergmann <arnd@...db.de>
To: Paul Gortmaker <paul.gortmaker@...driver.com>
Cc: "Greg Kroah-Hartman" <gregkh@...uxfoundation.org>,
Jiri Slaby <jslaby@...e.cz>, linux-kernel@...r.kernel.org,
Joe Perches <joe@...ches.com>,
Andy Whitcroft <apw@...onical.com>,
Geert Uytterhoeven <geert@...ux-m68k.org>
Subject: Re: [PATCH 4/4] checkpatch: only allow COMPILE_TEST in Kconfig dependency lines
On Thursday 04 July 2013, Paul Gortmaker wrote:
> The option CONFIG_COMPILE_TEST, added in commit 4bb1667255a
> ("build some drivers only when compile-testing") is meant to
> give a middle ground[1] between those who want the widest compile
> coverage possible (e.g. building sparc drivers for mips) and
> those who want dependencies to represent real world systems
> (e.g. don't allow me to see OMAP options when building x86).
>
> As such, this addition is meant to be used in dependency lines,
> properly or'd in with the real world hardware dependency. Those
> who select it, get wide compile coverage. Those who do not, get
> real world dependencies that match where the hardware is available
> and/or where the driver is useful.
>
> With that in mind, it is clear that this is _not_ to be used in
> any C code with "#ifdef CONFIG_COMPILE_TEST" etc. However there
> will (and already has been) instances of people thinking this is
> an OK practice[2]. So teach checkpatch to spot them as an error.
>
> [1] https://lkml.org/lkml/2013/3/7/456
> [2] https://lkml.org/lkml/2013/7/1/641
>
> Cc: Joe Perches <joe@...ches.com>
> Cc: Andy Whitcroft <apw@...onical.com>
> Cc: Arnd Bergmann <arnd@...db.de>
> Cc: Geert Uytterhoeven <geert@...ux-m68k.org>
> Cc: Jiri Slaby <jslaby@...e.cz>
> Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
> Signed-off-by: Paul Gortmaker <paul.gortmaker@...driver.com>
Acked-by: Arnd Bergmann <arnd@...db.de>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists