From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: multi_v5_defconfig: Enable support for MX21/MX27
Date: Wed, 30 Mar 2016 00:28:29 +0200 [thread overview]
Message-ID: <3101569.yyK0A7ozKe@wuerfel> (raw)
In-Reply-To: <1458991706-30109-1-git-send-email-jlu@pengutronix.de>
On Saturday 26 March 2016 12:28:25 Jan Luebbe wrote:
> Although the SoC support was already enabled, the drivers and machines
> were missing.
>
> Signed-off-by: Jan Luebbe <jlu@pengutronix.de>
>
I thought about applying this to the bug fix branch for 4.6, but
it doesn't seem urgent enough for that. Unless there is something
I'm missing about why we need it now, please have these merged
by the i.MX maintainers and sent to our next/defconfig branch for 4.7.
Arnd
next prev parent reply other threads:[~2016-03-29 22:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-26 11:28 [PATCH 1/2] ARM: multi_v5_defconfig: Enable support for MX21/MX27 Jan Luebbe
2016-03-26 11:28 ` [PATCH 2/2] ARM: multi_v5_defconfig: Enable recommended options for systemd Jan Luebbe
2016-04-12 11:57 ` Jan Lübbe
2016-04-12 14:26 ` Shawn Guo
2016-04-18 19:28 ` Arnd Bergmann
2016-03-29 22:28 ` Arnd Bergmann [this message]
2016-04-01 11:53 ` [PATCH 1/2] ARM: multi_v5_defconfig: Enable support for MX21/MX27 Sascha Hauer
2016-04-06 14:44 ` Shawn Guo
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=3101569.yyK0A7ozKe@wuerfel \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox