From: robert.jarzmik@free.fr (Robert Jarzmik)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH] ARM: pxa: add defconfig covering all the boards
Date: Fri, 01 Jan 2016 22:59:37 +0100 [thread overview]
Message-ID: <87vb7ddkqe.fsf@belgarion.home> (raw)
In-Reply-To: <22731126.qdCRlGzc5c@wuerfel> (Arnd Bergmann's message of "Thu, 31 Dec 2015 16:06:52 +0100")
Arnd Bergmann <arnd@arndb.de> writes:
> Sorry for the late reply. I think this is great and I'd like to just apply it.
> Can you re-send to arm at kernel.org if you're happy with that?
Yep.
> Looking at your description above, I see that you included pxa168_defconfig
> and pxa910_defconfig as well, but they are mach-mmp rather than mach-pxa.
> Can you check if that has added in anything we don't want?
Yep, done.
I added some pxa forgotten sound SoC machine code, I'll send a proper patch once
it passes my testers.
Cheers.
--
Robert
prev parent reply other threads:[~2016-01-01 21:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-20 16:54 [RFC PATCH] ARM: pxa: add defconfig covering all the boards Robert Jarzmik
2015-12-31 15:06 ` Arnd Bergmann
2016-01-01 21:59 ` Robert Jarzmik [this message]
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=87vb7ddkqe.fsf@belgarion.home \
--to=robert.jarzmik@free.fr \
--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).