All of lore.kernel.org
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] [ARM] mach-types: Re-add apf9328
Date: Thu, 13 Oct 2011 10:59:15 +0100	[thread overview]
Message-ID: <20111013095915.GO21648@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20111013090609.GT577@pengutronix.de>

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:
> > On Sat, Oct 08, 2011 at 09:26:21PM +0200, Wolfram Sang wrote:
> > > On Sat, Oct 08, 2011 at 05:19:48PM +0200, Gwenhael Goavec-Merou wrote:
> > > > 
> > > > Signed-off-by: Gwenhael Goavec-Merou <gwenhael.goavec-merou@armadeus.com>
> > > 
> > > 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.

  reply	other threads:[~2011-10-13  9:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-08 15:19 [PATCH 1/2] [ARM] mach-types: Re-add apf9328 Gwenhael Goavec-Merou
2011-10-08 15:19 ` [PATCH 2/2] [ARM] MX1:apf9328: Add i2c support Gwenhael Goavec-Merou
2011-10-08 19:27   ` Wolfram Sang
2011-10-11 15:26     ` gwenhael.goavec
2011-10-25  9:36   ` gwenhael.goavec
2011-10-25 11:47     ` Russell King - ARM Linux
2011-10-26  7:40     ` Sascha Hauer
2011-10-08 19:26 ` [PATCH 1/2] [ARM] mach-types: Re-add apf9328 Wolfram Sang
2011-10-08 22:07   ` Russell King - ARM Linux
2011-10-13  9:06     ` Uwe Kleine-König
2011-10-13  9:59       ` Russell King - ARM Linux [this message]
2011-10-17  8:44       ` Russell King - ARM Linux
2011-10-17  9:17         ` Russell King - ARM Linux
2011-10-21 10:10         ` Bedia, Vaibhav
2011-10-21 18:03           ` Russell King - ARM Linux
2011-10-24  8:19             ` Bedia, Vaibhav

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=20111013095915.GO21648@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 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.