linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] ARM: mxs: Add initial support for Bluegiga APX4 Development Kit
Date: Thu, 5 Jan 2012 11:31:06 +0000	[thread overview]
Message-ID: <20120105113106.GR11810@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20120104211800.GF11810@n2100.arm.linux.org.uk>

On Wed, Jan 04, 2012 at 09:18:00PM +0000, Russell King - ARM Linux wrote:
> On Wed, Jan 04, 2012 at 09:52:05PM +0800, Shawn Guo wrote:
> > On Mon, Dec 19, 2011 at 09:13:22AM +0000, Russell King - ARM Linux wrote:
> > > No.  It will be automatically removed from any update as long as it does
> > > not conform to the requirements - that is, in this case, the strings
> > > being out of sync indentified in the message to which you replied to.
> > > 
> > > Someone needs to tell me what the correct entry is supposed to look like.
> > > 
> > Hi Russell,
> > 
> > Any chance to have APX4DEVKIT included in your patch 'ARM: Update
> > mach-types' for 3.3?
> 
> As it appears when I run the update script, the answer is yes.  I'll
> update the commit in the next couple of days (I want to reduce the
> number of times I re-merge the tree now that I've a git-rerere immune
> conflict to deal with.)

I'll change that - as 3.2 was released last night.  I'm not going to
update mach-types now as that would be suicide - updating it will
mean a bunch of entries will be deleted, and we don't know whether that
will cause build failures.

So... not this side of the merge window.

  reply	other threads:[~2012-01-05 11:31 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-13  9:02 [PATCH v3] ARM: mxs: Add initial support for Bluegiga APX4 Development Kit Lauri Hintsala
2011-12-16  6:07 ` Lauri Hintsala
2011-12-16  6:53   ` Shawn Guo
2011-12-19  7:13 ` Shawn Guo
2011-12-19  7:13   ` Lauri Hintsala
2011-12-19  9:19     ` Shawn Guo
2011-12-19  9:13       ` Russell King - ARM Linux
2011-12-19  9:15         ` Russell King - ARM Linux
2011-12-19  9:32           ` Lauri Hintsala
2011-12-19  9:44           ` Shawn Guo
2011-12-19 11:18             ` Veli-Pekka Peltola
2012-01-04 13:52         ` Shawn Guo
2012-01-04 21:18           ` Russell King - ARM Linux
2012-01-05 11:31             ` Russell King - ARM Linux [this message]
2012-01-05 12:15               ` Shawn Guo
2012-01-05 12:08                 ` Lauri Hintsala
2012-03-30 13:13               ` Shawn Guo
2012-03-30 13:15                 ` Russell King - ARM Linux
2012-03-30 13:20                   ` Russell King - ARM Linux
2012-04-26  7:42                     ` Lauri Hintsala
2012-04-26  7:48                       ` Shawn Guo
2012-04-26  7:55                         ` Lauri Hintsala
2012-03-30 13:22                   ` Shawn Guo
2012-03-30 13:28                     ` Russell King - ARM Linux
2012-03-30 22:43                       ` Nicolas Pitre

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=20120105113106.GR11810@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).