From: "Tobin C. Harding" <me@tobin.cc>
To: Joe Perches <joe@perches.com>
Cc: linux-kernel@vger.kernel.org, Andy Whitcroft <apw@canonical.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: checkpatch changes for 4.16
Date: Thu, 1 Feb 2018 10:23:58 +1100 [thread overview]
Message-ID: <20180131232358.GA29988@eros> (raw)
In-Reply-To: <1517438936.7489.8.camel@perches.com>
On Wed, Jan 31, 2018 at 02:48:56PM -0800, Joe Perches wrote:
> On Thu, 2018-02-01 at 08:46 +1100, Tobin C. Harding wrote:
> > Hi Joe,
> >
> > Can I please bother you with a maintainer question. I know everyone is
> > super busy right now, I'm asking for a smidgen of your time instead of
> > doing it wrong and taking up some of Linus' time since it's merge window
> > and all that.
> >
> > I have the checkpatch set queued ready to do a GIT PULL to Linus. My
> > concern is that the subject line may not be unique if checkpatch changes
> > are coming in from various trees this merge window. I have tagged the
> > pull request with
>
> Personally, I think you could let Andrew Morton pick them
> up as very few patches for checkpatch go in any other way.
ok no worries. I'll leave it until a few rc's are out then send to Andrew.
> What patches are you submitting again?
>
> Is it just
>
> commit 7b1924a1d930 ("vsprintf: add printk specifier %px")
>
> or is there something else?
d94e97bc9ede checkpatch: add sub routine get_stat_real()
d0e27c47f5b9 checkpatch: add sub routine get_stat_here()
986b3b5b7d7a checkpatch: warn for use of %px
26c1cf882d79 checkpatch: add check for tag Co-Developed-by
I thought it was odd when you said they could go in through _any_
tree. Not to worry, it's not urgent.
Thanks for the responce.
Tobin
next prev parent reply other threads:[~2018-01-31 23:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 21:46 checkpatch changes for 4.16 Tobin C. Harding
2018-01-31 22:48 ` Joe Perches
2018-01-31 23:23 ` Tobin C. Harding [this message]
2018-01-31 23:56 ` Joe Perches
2018-02-01 0:10 ` Tobin C. Harding
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=20180131232358.GA29988@eros \
--to=me@tobin.cc \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=joe@perches.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox