[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20091220201052.GA5665@elte.hu>
Date: Sun, 20 Dec 2009 21:10:52 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Joe Perches <joe@...ches.com>
Cc: Andy Whitcroft <apw@...onical.com>, mingo@...hat.com,
hpa@...or.com, linux-kernel@...r.kernel.org,
torvalds@...ux-foundation.org, peterz@...radead.org, efault@....de,
akpm@...ux-foundation.org, tglx@...utronix.de
Subject: Re: [PATCH] scripts/checkpatch.pl: Add WARN on printk format split
on multiple lines
* Joe Perches <joe@...ches.com> wrote:
> On Sun, 2009-12-20 at 20:15 +0100, Ingo Molnar wrote:
> > Checkpatch should warn about printk
> > lines that end with a '"', those are almost always a sign of some ill-advised
> > break-the-string artifact.
>
> Perhaps something like this:
>
> diff from Andy Whitcroft's testing script,
> where logFunctions is defined.
> http://www.kernel.org/pub/linux/kernel/people/apw/checkpatch/checkpatch.pl-testing
>
> --- a/scripts/checkpatch.pl-testing 2009-12-20 11:35:28.000000000 -0800
> +++ b/scripts/checkpatch.pl-testing 2009-12-20 11:35:46.000000000 -0800
> @@ -1398,6 +1398,11 @@
> WARN("line over 80 characters\n" . $herecurr);
> }
>
> +#Logging function format split over multiple lines
> + if ($line =~ /^\+\s*$logFunctions.*"\s*$/) {
> + WARN("Don't split logging function format\n" . $herecurr);
> + }
> +
Havent tested it but this check would be lovely to have.
Acked-by: Ingo Molnar <mingo@...e.hu>
Ingo
--
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