From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: at91 material for 3.1
Date: Wed, 28 Sep 2011 10:27:37 +0200 [thread overview]
Message-ID: <4E82DA79.70006@atmel.com> (raw)
Hi Arnd,
I have two little patches about Kconfig and one defconfig that are
suitable for a 3.1 inclusion.
I wonder if you plan a pull request to Linus before 3.1-final?
If yes, would you prefer each patch in a feature branch on its own
(at91-kconfig, at91-defconfig for instance) or a generic at91-fixes?
Thanks, best regards,
--
Nicolas Ferre
next reply other threads:[~2011-09-28 8:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-28 8:27 Nicolas Ferre [this message]
2011-09-28 13:00 ` at91 material for 3.1 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=4E82DA79.70006@atmel.com \
--to=nicolas.ferre@atmel.com \
--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).