[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f9803189e589cc719fc9a561003317a81d2da07e.camel@perches.com>
Date: Tue, 18 Aug 2020 01:07:17 -0700
From: Joe Perches <joe@...ches.com>
To: Jerome Forissier <jerome@...issier.org>,
Andy Whitcroft <apw@...onical.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] checkpatch: add --kconfig-prefix
On Tue, 2020-08-18 at 09:50 +0200, Jerome Forissier wrote:
>
> On 8/18/20 9:43 AM, Jerome Forissier wrote:
> > Kconfig allows to customize the CONFIG_ prefix via the $CONFIG_
> > environment variable. Out-of-tree projects may therefore use Kconfig
> > with a different prefix, or they may use a custom configuration tool
> > which does not use the CONFIG_ prefix at all. Such projects may still
> > want to adhere to the Linux kernel coding style and run checkpatch.pl.
> >
> > One example is OP-TEE [1] which does not use Kconfig but does have
> > configuration options prefixed with CFG_. It also mostly follows the
> > kernel coding style and therefore being able to use checkpatch is quite
> > valuable.
> >
> > To make this possible, add the --kconfig-prefix command line option.
>
> (Oh I forgot to add the link here :-/ sorry about that. Let me know if
> you want me to resend.)
>
> [1] https://github.com/OP-TEE/optee_os
It's probably not important enough to bother.
A trivial search on "OP-TEE" works.
So I think it's fine, but if you feel like it,
go ahead.
Joe
Powered by blists - more mailing lists