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 18:23:04 +0100 [thread overview]
Message-ID: <20120830172304.GA18957@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20120830165224.GR19437@titan.lakedaemon.net>
On Thu, Aug 30, 2012 at 12:52:24PM -0400, Jason Cooper wrote:
> On Thu, Aug 30, 2012 at 07:14:47AM +0200, Andrew Lunn wrote:
> > Tools like kisskb are good at finding build regressions in the kernel
> > sources. However, regressions in the DT desscriptions are not found,
> > because generally these build systems don't build the DT binary blobs.
> >
> > Extend the ARM all target to build all enabled DTB files.
> >
> > Signed-off-by: Andrew Lunn <andrew@lunn.ch>
>
> Acked-by: Jason Cooper <jason@lakedaemon.net>
>
> 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.
> It does depend on
> having dtc built. A patch already exists to build dtc on demand, but
> I'm not sure if it has made it into mainline yet. It may be in
> Russell's queue.
At the moment, the only stuff I have outstanding for -rc is:
36418c5 ARM: 7499/1: mm: Fix vmalloc overlap check for !HIGHMEM
df547e0 ARM: 7503/1: mm: only flush both pmd entries for classic MMU
ae3790b ARM: 7502/1: contextidr: avoid using bfi instruction during notifier
dbece45 ARM: 7501/1: decompressor: reset ttbcr for VMSA ARMv7 cores
d968d2b ARM: 7497/1: hw_breakpoint: allow single-byte watchpoints on all addressbf88011 ARM: 7496/1: hw_breakpoint: don't rely on dfsr to show watchpoint accessa849088 ARM: Fix ioremap() of address zero
I have nothing queued for dtc building, and there's no sign of anything
new in the patch system.
next prev parent reply other threads:[~2012-08-30 17:23 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 [this message]
2012-08-30 18:37 ` Jason Cooper
2012-08-30 19:14 ` Russell King - ARM Linux
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=20120830172304.GA18957@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).