All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Whitcroft <apw@shadowen.org>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] checkpatch: nested structs
Date: Tue, 8 Apr 2008 18:35:48 +0100	[thread overview]
Message-ID: <20080408173548.GG17915@shadowen.org> (raw)
In-Reply-To: <282cb105d4016d63a4c24442e244d157ef3aebe8.1207666528.git.jengelh@computergmbh.de>

On Tue, Apr 08, 2008 at 04:55:30PM +0200, Jan Engelhardt wrote:
> This is required for nested struct/union compounds.
> ---
>  scripts/checkpatch.pl |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> index 58a9494..cf78e86 100755
> --- a/scripts/checkpatch.pl
> +++ b/scripts/checkpatch.pl
> @@ -1582,7 +1582,7 @@ sub process {
>  
>  # closing brace should have a space following it when it has anything
>  # on the line
> -		if ($line =~ /}(?!(?:,|;|\)))\S/) {
> +		if ($line =~ /}+(?!(?:,|;|\)))\S/) {
>  			ERROR("space required after that close brace '}'\n" . $herecurr);
>  		}

If my eyes are not lying then you have added is a + after the first },
as this is an unanchored match I would expect that to match in exactly
the same places.  Hmm, well I guess that it would allow two or more close
braces to abutt.  Can you give me an example of somethign which would
require this?

-apw

  reply	other threads:[~2008-04-08 17:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-08 14:55 [PATCH 1/1] checkpatch: nested structs Jan Engelhardt
2008-04-08 17:35 ` Andy Whitcroft [this message]
2008-04-08 17:59   ` Jan Engelhardt

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=20080408173548.GG17915@shadowen.org \
    --to=apw@shadowen.org \
    --cc=jengelh@computergmbh.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.