All of lore.kernel.org
 help / color / mirror / Atom feed
From: stigge@antcom.de (Roland Stigge)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] LPC32xx fixes for v3.3-rc4
Date: Mon, 27 Feb 2012 17:46:56 +0100	[thread overview]
Message-ID: <4F4BB380.30803@antcom.de> (raw)
In-Reply-To: <201202271409.52470.arnd@arndb.de>

Hi Arnd and Wolfram,

thanks for your notes!

On 02/27/2012 03:09 PM, Arnd Bergmann wrote:
> The patch look all good, but it's not clear where you would like to
> see them applied. The largest one "ARM: LPC32xx: Fix missing and bad
> LPC32XX macros" looks like it is only of cosmetic nature and should
> go into the next/fixes-non-critical branch for v3.4, while the
> others look like they are requried for v3.3

Right. I replaced the mentioned branch with

* lpc32xx/fixes-non-critical (singled out the macros fixes, for next)
* lpc32xx/fixes (the remaining 5 patches as immediate fixes)

Please note that although it's a typo fix in the macros, it's also an
internal API change.

I also added the stable-CC to the "lpc32xx/fixes" and added the note
about NXP's HW bugfix as suggested by Wolfram.

I'll regenerate the pull request. Please tell me if you also like to
have the patches re-posted.

Thanks in advance,

Roland

  reply	other threads:[~2012-02-27 16:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-25 16:30 [GIT PULL] LPC32xx fixes for v3.3-rc4 Roland Stigge
2012-02-27 14:09 ` Arnd Bergmann
2012-02-27 16:46   ` Roland Stigge [this message]
2012-02-27 17:43     ` Arnd Bergmann
     [not found]   ` <4F4BB721.6020606@antcom.de>
2012-02-27 17:45     ` [GIT PULL] LPC32xx fixes for v3.3-rc5 Arnd Bergmann
     [not found]   ` <4F4BB7E8.1040606@antcom.de>
2012-02-27 18:00     ` [GIT PULL] LPC32xx fixes-non-critical " Arnd Bergmann

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=4F4BB380.30803@antcom.de \
    --to=stigge@antcom.de \
    --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.