From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] AT91: patches for v2.6.38-rc1
Date: Fri, 14 Jan 2011 18:04:55 +0000 [thread overview]
Message-ID: <20110114180455.GL15996@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <4D308F30.6070503@atmel.com>
On Fri, Jan 14, 2011 at 07:00:16PM +0100, Nicolas Ferre wrote:
> Hi Russell,
>
> Can you please pull those little changes for AT91? They add two
> new boards already discussed on the mailing list and a little
> cleanup patch:
Has this already been in linux-next?
We should only be merging new code during a merge window which has
already had visibility in linux-next, with the exception of bug fixes
and regression fixes.
Regression fixes can be merged at any time provided they're obvious.
Any regression fix should be acceptable during the merge window.
Bug fixes any time up until (I'd say) the last week of the -rc series.
next prev parent reply other threads:[~2011-01-14 18:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-14 18:00 [GIT PULL] AT91: patches for v2.6.38-rc1 Nicolas Ferre
2011-01-14 18:04 ` Russell King - ARM Linux [this message]
2011-01-14 18:14 ` Nicolas Ferre
2011-01-14 18:17 ` Russell King - ARM Linux
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=20110114180455.GL15996@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