public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Whitcroft <apw@shadowen.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-kernel@vger.kernel.org, torvalds@osdl.org
Subject: Re: [RFC/PATCH] Update coding standard to avoid ungrepable printk format strings
Date: Mon, 25 Feb 2008 05:30:52 +0000	[thread overview]
Message-ID: <20080225053052.GB2604@shadowen.org> (raw)
In-Reply-To: <20080222132612.GA11717@basil.nowhere.org>

On Fri, Feb 22, 2008 at 02:26:12PM +0100, Andi Kleen wrote:

> At some point checkpatch.pl would need to be updated to know about this
> exception too, that would be the next step.

Cirtainly we have exceptions for docstrings, so that shouldn't be a
problem if this were accepted.

-apw

      parent reply	other threads:[~2008-02-25  5:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-22 13:26 [RFC/PATCH] Update coding standard to avoid ungrepable printk format strings Andi Kleen
2008-02-22 13:53 ` Stefan Richter
2008-02-22 14:01   ` Andi Kleen
2008-02-22 15:02 ` Alan Cox
2008-02-22 16:58 ` Joe Perches
2008-02-23 12:55 ` Christer Weinigel
2008-02-25  5:29   ` Andy Whitcroft
2008-02-25  5:30 ` Andy Whitcroft [this message]

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=20080225053052.GB2604@shadowen.org \
    --to=apw@shadowen.org \
    --cc=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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