From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] LPC32xx fixes for v3.3-rc4
Date: Mon, 27 Feb 2012 14:09:52 +0000 [thread overview]
Message-ID: <201202271409.52470.arnd@arndb.de> (raw)
In-Reply-To: <4F490CC0.5050303@antcom.de>
On Saturday 25 February 2012, Roland Stigge wrote:
> the fixes for LPC32xx that I just posted as patches are also available as a
> git branch to pull from as described below.
>
> The following changes since commit b01543dfe67bb1d191998e90d20534dc354de059:
>
> Linux 3.3-rc4 (2012-02-18 15:53:33 -0800)
>
> are available in the git repository at:
>
> git://git.antcom.de/linux-2.6.git lpc32xx-fixes
>
> for you to fetch changes up to 3eddb16b7b275162c62f67bb75cc6bbe0ef8c075:
>
> ARM: LPC32xx: serial.c: Fixed loop limit (2012-02-25 16:32:44 +0100)
Hi Roland,
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, some of them
also for earlier versions. Remember that any bug fix that applies
to older kernels should have a "Cc: stable at vger.kernel.org" tag
so that Greg can automatically pick up the fixes and port them
to the stable and longterm releases.
Arnd
next prev parent reply other threads:[~2012-02-27 14:09 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 [this message]
2012-02-27 16:46 ` Roland Stigge
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=201202271409.52470.arnd@arndb.de \
--to=arnd@arndb.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.