From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: Build dtb files in all target
Date: Thu, 30 Aug 2012 20:14:12 +0100 [thread overview]
Message-ID: <20120830191412.GC18957@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20120830183711.GY19437@titan.lakedaemon.net>
On Thu, Aug 30, 2012 at 02:37:11PM -0400, Jason Cooper wrote:
> On Thu, Aug 30, 2012 at 06:23:04PM +0100, Russell King - ARM Linux wrote:
> > On Thu, Aug 30, 2012 at 12:52:24PM -0400, Jason Cooper wrote:
> > > I've CC'd stable to see if they want to pick this up.
> >
> > That's not how stable works - and you'll probably receive a standard form
> > whinge from them about that. Please read up on the submission requirements
> > to the stable kernel trees.
>
> Ah, thanks. usually, I just add the Cc: line for fixes I send to
> arm-soc. Since this patch affects more than just kirkwood/marvell, I
> didn't feel it was appropriate to pull it in through my tree.
Yes, you put the Cc: line in the commit, but you don't actually send it
to that address. The only time that you do mail that address is when
the commit is _in_ mainline and it doesn't have the Cc: tag or the stable
team haven't picked it up.
> I submitted a patch six months ago for the exact same thing and was
> informed that others already had a pending patch in your queue for it.
> However, I can't for the life of me locate the thread atm. I remember
> it because it was the first patch I did that needed to go into your
> queue instead of through arm-soc. Obviously, I did something horribly
> wrong. ;-)
I don't see anything in there for it - I tried searching for patches
containing 'dtbs' and the latest one it found was 7152/1 on 8th
November. I also see no notifications from the patch system for a
patch from you...
next prev parent reply other threads:[~2012-08-30 19:14 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-30 5:14 [PATCH v2] ARM: Build dtb files in all target Andrew Lunn
2012-08-30 16:52 ` Jason Cooper
2012-08-30 17:23 ` Russell King - ARM Linux
2012-08-30 18:37 ` Jason Cooper
2012-08-30 19:14 ` Russell King - ARM Linux [this message]
2012-08-30 19:40 ` Jason Cooper
2012-08-31 21:11 ` Ben Hutchings
2012-08-31 22:32 ` Russell King - ARM Linux
2012-09-01 14:20 ` Ben Hutchings
2012-09-01 15:25 ` Russell King - ARM Linux
2012-09-01 16:32 ` Jonathan Nieder
2012-09-01 18:22 ` Russell King - ARM Linux
2012-09-01 18:38 ` Jonathan Nieder
2012-09-01 20:11 ` Russell King - ARM Linux
2012-09-02 6:30 ` When to cc stable@vger.kernel.org (Re: [PATCH v2] ARM: Build dtb files in all target) Jonathan Nieder
2012-09-02 13:54 ` [PATCH v2] ARM: Build dtb files in all target Ben Hutchings
2012-09-02 17:04 ` Russell King - ARM Linux
2012-09-02 17:26 ` Ben Hutchings
2012-09-02 18:05 ` Russell King - ARM Linux
2012-09-02 19:14 ` Uwe Kleine-König
2012-09-02 23:58 ` Greg KH
2012-08-30 18:03 ` Greg KH
2012-09-01 14:49 ` Andrew Lunn
2012-09-03 12:21 ` Dave Martin
2012-09-03 19:55 ` Jason Cooper
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=20120830191412.GC18957@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).