linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: joe@perches.com (Joe Perches)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/8] arm: Convert pr_warning to pr_warn
Date: Tue, 16 Sep 2014 13:08:55 -0700	[thread overview]
Message-ID: <1410898135.16519.14.camel@joe-AO725> (raw)
In-Reply-To: <20140916195737.GO12361@n2100.arm.linux.org.uk>

On Tue, 2014-09-16 at 20:57 +0100, Russell King - ARM Linux wrote:
> On Tue, Sep 16, 2014 at 09:18:01AM -0700, Joe Perches wrote:
> > On Tue, 2014-09-16 at 17:07 +0100, Russell King - ARM Linux wrote:
> > > any chance you could add a KernelVersion: tag somewhere in the
> > > commit message and throw it at patches at arm.linux.org.uk so it doesn't
> > > get lost?
> > 
> > There are no commit logs with a KernelVersion: tag
> > in all of git history.
> 
> Right, that's not it's purpose.
> 
> > What do you think a KernelVersion: tag is and what
> > would it be used for?
> 
> It's for that email address to know which kernel version the patch
> was generated against, which is useful information when I come to
> apply it.  It gets filtered out from the commit message.  It can go
> anywhere, even below the -- line.

> If you don't want to cooperate, you will have to rely on my notoriously
> bad email skills to scan the mailing list for random patches to apply
> some time (maybe days or even weeks) later after you send your message.
> Which just won't happen.  It's why I wrote scripts which are some 20
> years old to solve my bad email patch handling skills.

I received your patchbot's reply about 15 minutes
before you sent this.

I suggest you might move one year to patchwork
(ie: https://patchwork.kernel.org/project/linux-arm-kernel/list/)
and adapt that as necessary, but whatever works
for you.

btw:

patches at arm.linux.org.uk is not documented at all
in the kernel sources.  You could fix that if you
want other people to know what you do.

  reply	other threads:[~2014-09-16 20:08 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-13 18:31 [PATCH 0/8] arm: Convert pr_warning to pr_warn Joe Perches
2014-09-13 18:31 ` [PATCH 1/8] " Joe Perches
2014-09-15 15:56   ` Will Deacon
2014-09-15 16:02     ` Joe Perches
2014-09-16 16:07     ` Russell King - ARM Linux
2014-09-16 16:18       ` Joe Perches
2014-09-16 19:24         ` Uwe Kleine-König
2014-09-16 19:57         ` Russell King - ARM Linux
2014-09-16 20:08           ` Joe Perches [this message]
2014-09-13 18:31 ` [PATCH 2/8] arm: mach-davinci: " Joe Perches
2014-09-13 18:31 ` [PATCH 3/8] arm: mach-ep93xx: " Joe Perches
2014-09-13 18:31 ` [PATCH 4/8] arm: mach-imx: " Joe Perches
2014-09-16  1:51   ` Shawn Guo
2014-09-13 18:31 ` [PATCH 5/8] arm: mach-omap2: " Joe Perches
2014-09-18 16:54   ` Tony Lindgren
2014-09-13 18:31 ` [PATCH 6/8] arm: mach-orion5x: " Joe Perches
2014-09-13 19:16   ` Andrew Lunn
2014-09-13 21:51   ` Jason Cooper
2014-09-13 18:31 ` [PATCH 7/8] arm: mach-pxa: " Joe Perches
2014-09-21 17:02   ` Robert Jarzmik
2014-09-13 18:31 ` [PATCH 8/8] arm: mach-u300: " Joe Perches
2014-09-23 15:10   ` Linus Walleij

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=1410898135.16519.14.camel@joe-AO725 \
    --to=joe@perches.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).