mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Przemek Kitszel <przemyslaw.kitszel@intel.com>,
	Andy Whitcroft <apw@canonical.com>,
	linux-kernel@vger.kernel.org
Cc: Jacob Keller <jacob.e.keller@intel.com>,
	Dwaipayan Ray <dwaipayanray1@gmail.com>,
	Lukas Bulwahn <lukas.bulwahn@gmail.com>
Subject: Re: [PATCH] checkpatch: don't complain on _Static_assert and _Generic use
Date: Tue, 28 Nov 2023 16:48:53 -0800	[thread overview]
Message-ID: <facf6ef0c3775b02b14022a5b901eba309fd1c68.camel@perches.com> (raw)
In-Reply-To: <812f7729-1e48-bdcf-18be-c94c57f5e5f2@intel.com>

On Tue, 2023-11-28 at 11:25 +0100, Przemek Kitszel wrote:
> On 11/28/23 01:46, Joe Perches wrote:
> > On Mon, 2023-11-27 at 16:18 +0100, Przemek Kitszel wrote:
> > > Improve CamelCase recognition logic to avoid reporting on _Static_assert()
> > > and _Generic() use.
> > > 
> > > Other C keywords, such as _Bool, are intentionally omitted, as those
> > > should be rather avoided in new source code.
> > []
> > > diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> > []
> > > @@ -5839,6 +5839,8 @@ sub process {
> > >   #CamelCase
> > >   			if ($var !~ /^$Constant$/ &&
> > >   			    $var =~ /[A-Z][a-z]|[a-z][A-Z]/ &&
> > > +#Ignore C keywords
> > > +			    $var !~ /_Static_assert|_Generic/ &&
> > 
> > You'll need
> > 
> > 			    $var != /^(?:_Static_assert|_Generic)$/ &&

Hi again.

btw:  Looks like adding _Pragma would be useful too.

$ git grep -ohP '\b_\w+' -- '*.[ch]' | \
  sort | uniq -c | sort -rn | \
  grep -P '[a-z][A-Z]|[A-Z][a-z]' | \
  head -30
    377 __Value
    206 __pH2CCmd
    152 __pTxDesc
     78 _Pragma
     54 __pRxDesc
     52 __pRxStatusDesc
     50 _Generic
     48 _Static_assert
     41 _PyUnicode_FromString
     30 _pEleStart
     29 _PyLong_FromLong
     26 _NonStandardParameter
     24 _txOff
     24 _TransportAddress
     23 _txOn
     23 _Bool
     22 _Lxx
     21 _Exx
     19 _min_uV
     18 _StateArray
     18 _NonClockInfoArray
     18 _ClockInfoArray
     16 _8Mx32
     16 _32Mx16
     16 _16Mx32
     16 _16Mx16
     15 _REGIc
     13 _step_uV
     13 _Set_Drv_Extra
     13 __PageMovable


  parent reply	other threads:[~2023-11-29  0:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-27 15:18 Przemek Kitszel
2023-11-28  0:46 ` Joe Perches
2023-11-28 10:25   ` Przemek Kitszel
2023-11-28 10:52     ` Joe Perches
2023-11-29  0:48     ` Joe Perches [this message]
2023-11-29  8:58 ` Rasmus Villemoes

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=facf6ef0c3775b02b14022a5b901eba309fd1c68.camel@perches.com \
    --to=joe@perches.com \
    --cc=apw@canonical.com \
    --cc=dwaipayanray1@gmail.com \
    --cc=jacob.e.keller@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukas.bulwahn@gmail.com \
    --cc=przemyslaw.kitszel@intel.com \
    /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®