From: Andy Whitcroft <apw@canonical.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: mike@compulab.co.il, linux-kernel@vger.kernel.org
Subject: Re: checkpatch --file warns about p0 patch
Date: Sat, 28 Feb 2009 23:55:26 +0000 [thread overview]
Message-ID: <20090228235526.GA6023@shadowen.org> (raw)
In-Reply-To: <20090223150405.ce90a2c0.akpm@linux-foundation.org>
On Mon, Feb 23, 2009 at 03:04:05PM -0800, Andrew Morton wrote:
> On Mon, 23 Feb 2009 14:43:12 +0000
> Andy Whitcroft <apw@canonical.com> wrote:
>
> > Hmm, that should already be fixed in the version Andrew Morton has.
>
> Hmm, all of these:
>
> checkpatch-make-in_atomic-ok-in-the-core.patch
> checkpatch-do-not-warn-about-p0-patches-when-checking-files.patch
> checkpatch-correctly-handle-type-spacing-in-the-face-of-modifiers.patch
> checkpatch-pointer-type-star-may-have-modifiers-following.patch
> checkpatch-a-modifier-is-not-an-identifier-at-the-end-of-a-type.patch
> checkpatch-extend-attribute-testing-to-all-modifiers.patch
> checkpatch-add-__ref-as-a-sparse-modifier.patch
> checkpatch-version-028.patch
>
> apart from perhaps checkpatch-add-__ref-as-a-sparse-modifier.patch look
> like bugfixes. So I suppose we should slip them into 2.6.29, yes?
Yes those are all bugfixes. If we can get them in that would be good.
-apw
prev parent reply other threads:[~2009-02-28 23:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-23 14:20 checkpatch --file warns about p0 patch Mike Rapoport
2009-02-23 14:43 ` Andy Whitcroft
2009-02-23 14:56 ` Mike Rapoport
2009-02-23 23:04 ` Andrew Morton
2009-02-28 23:55 ` 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=20090228235526.GA6023@shadowen.org \
--to=apw@canonical.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mike@compulab.co.il \
/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