From: Joe Perches <joe@perches.com>
To: Jerome Forissier <jerome@forissier.org>,
Andy Whitcroft <apw@canonical.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] checkpatch: add --kconfig-prefix
Date: Tue, 18 Aug 2020 01:07:17 -0700 [thread overview]
Message-ID: <f9803189e589cc719fc9a561003317a81d2da07e.camel@perches.com> (raw)
In-Reply-To: <266350d9-c770-6a29-b784-46de2b005e39@forissier.org>
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
next prev parent reply other threads:[~2020-08-18 8:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-17 9:50 [PATCH] checkpatch: get CONFIG_ prefix from the environment Jerome Forissier
2020-08-17 14:09 ` Joe Perches
2020-08-17 14:24 ` Jerome Forissier
2020-08-17 15:33 ` [PATCH v2] checkpatch: add --kconfig-prefix Jerome Forissier
2020-08-17 16:19 ` Joe Perches
2020-08-18 7:43 ` [PATCH v3] " Jerome Forissier
2020-08-18 7:50 ` Jerome Forissier
2020-08-18 8:07 ` Joe Perches [this message]
2020-08-18 8:03 ` Joe Perches
2020-08-18 8:17 ` [PATCH v4] " Jerome Forissier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f9803189e589cc719fc9a561003317a81d2da07e.camel@perches.com \
--to=joe@perches.com \
--cc=apw@canonical.com \
--cc=jerome@forissier.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®