Thread (16 messages) flat view 16 messages, 6 authors, 2011-10-26
STALE5426d

[PATCH 1/2] [ARM] mach-types: Re-add apf9328

From: Russell King - ARM Linux <hidden>
Date: 2011-10-13 09:59:15

On Thu, Oct 13, 2011 at 11:06:09AM +0200, Uwe Kleine-K?nig wrote:
On Sat, Oct 08, 2011 at 11:07:22PM +0100, Russell King - ARM Linux wrote:
quoted
On Sat, Oct 08, 2011 at 09:26:21PM +0200, Wolfram Sang wrote:
quoted
On Sat, Oct 08, 2011 at 05:19:48PM +0200, Gwenhael Goavec-Merou wrote:
quoted
Signed-off-by: Gwenhael Goavec-Merou <redacted>
I think this file is maintained by Russell, yet I want to ack that the entry
below is missing for building mx1_defconfig. Found that, too.
The thing is - read the comments at the top of the file.  There's hints
there as to what will happen if you patch the file.  The hint is
'automatically generated'.  So when I next update the file, any patches
done to the file will be wiped out.
Currently the id is still missing in your for-next branch and it is
marked as "mainlined" on http://www.arm.linux.org.uk/developer/machines/
(906).

That means that the next update should include the id, right?
Not if it's a buggered entry - which it doesn't appear to be.  The problem
is that now that I've stopped manually editing out the buggered entries,
favouring doing it automatically, any update to the file ends up breaking
the damned thing for someone.

It's rather too late in the cycle for me to commit an update now - I
suspect doing so will upset a lot of people.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help