All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Will Deacon <will.deacon@arm.com>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/8] arm: Convert pr_warning to pr_warn
Date: Tue, 16 Sep 2014 09:18:01 -0700	[thread overview]
Message-ID: <1410884281.16519.2.camel@joe-AO725> (raw)
In-Reply-To: <20140916160759.GJ12361@n2100.arm.linux.org.uk>

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@arm.linux.org.uk so it doesn't
> get lost?

There are no commit logs with a KernelVersion: tag
in all of git history.

What do you think a KernelVersion: tag is and what
would it be used for?



WARNING: multiple messages have this Message-ID (diff)
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 09:18:01 -0700	[thread overview]
Message-ID: <1410884281.16519.2.camel@joe-AO725> (raw)
In-Reply-To: <20140916160759.GJ12361@n2100.arm.linux.org.uk>

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.

What do you think a KernelVersion: tag is and what
would it be used for?

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

Thread overview: 45+ 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 ` Joe Perches
2014-09-13 18:31 ` Joe Perches
2014-09-13 18:31 ` [PATCH 1/8] " Joe Perches
2014-09-13 18:31   ` Joe Perches
2014-09-15 15:56   ` Will Deacon
2014-09-15 15:56     ` Will Deacon
2014-09-15 16:02     ` Joe Perches
2014-09-15 16:02       ` Joe Perches
2014-09-16 16:07     ` Russell King - ARM Linux
2014-09-16 16:07       ` Russell King - ARM Linux
2014-09-16 16:18       ` Joe Perches [this message]
2014-09-16 16:18         ` Joe Perches
2014-09-16 19:24         ` Uwe Kleine-König
2014-09-16 19:24           ` Uwe Kleine-König
2014-09-16 19:57         ` Russell King - ARM Linux
2014-09-16 19:57           ` Russell King - ARM Linux
2014-09-16 20:08           ` Joe Perches
2014-09-16 20:08             ` Joe Perches
2014-09-13 18:31 ` [PATCH 2/8] arm: mach-davinci: " Joe Perches
2014-09-13 18:31   ` Joe Perches
2014-09-13 18:31 ` [PATCH 3/8] arm: mach-ep93xx: " Joe Perches
2014-09-13 18:31   ` Joe Perches
2014-09-13 18:31 ` [PATCH 4/8] arm: mach-imx: " Joe Perches
2014-09-13 18:31   ` Joe Perches
2014-09-16  1:51   ` Shawn Guo
2014-09-16  1:51     ` Shawn Guo
2014-09-13 18:31 ` [PATCH 5/8] arm: mach-omap2: " Joe Perches
2014-09-13 18:31   ` Joe Perches
2014-09-18 16:54   ` Tony Lindgren
2014-09-18 16:54     ` Tony Lindgren
2014-09-13 18:31 ` [PATCH 6/8] arm: mach-orion5x: " Joe Perches
2014-09-13 18:31   ` Joe Perches
2014-09-13 19:16   ` Andrew Lunn
2014-09-13 19:16     ` Andrew Lunn
2014-09-13 21:51   ` Jason Cooper
2014-09-13 21:51     ` Jason Cooper
2014-09-13 18:31 ` [PATCH 7/8] arm: mach-pxa: " Joe Perches
2014-09-13 18:31   ` Joe Perches
2014-09-21 17:02   ` Robert Jarzmik
2014-09-21 17:02     ` Robert Jarzmik
2014-09-13 18:31 ` [PATCH 8/8] arm: mach-u300: " Joe Perches
2014-09-13 18:31   ` Joe Perches
2014-09-23 15:10   ` Linus Walleij
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=1410884281.16519.2.camel@joe-AO725 \
    --to=joe@perches.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mingo@redhat.com \
    --cc=paulus@samba.org \
    --cc=will.deacon@arm.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.