From: lauri.hintsala@bluegiga•com (Lauri Hintsala)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v3] ARM: mxs: Add initial support for Bluegiga APX4 Development Kit
Date: Thu, 05 Jan 2012 14:08:54 +0200 [thread overview]
Message-ID: <4F0592D6.6040108@bluegiga.com> (raw)
In-Reply-To: <20120105121523.GE1729@S2101-09.ap.freescale.net>
On 01/05/2012 02:15 PM, Shawn Guo wrote:
>> So... not this side of the merge window.
>
> Ok, thanks for letting us know.
>
> Lauri,
>
> It seems that you have to split the mxs_defconfig change out, so that
> I can send the patch to Arnd without waiting for mach-types update.
> And we can send mxs_defconfig update later when mach-types update hits
> mainline.
Ok, I'll do immediately new patch without mxs_defconfig change.
Lauri
next prev parent reply other threads:[~2012-01-05 12:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-13 9:02 [PATCH v3] ARM: mxs: Add initial support for Bluegiga APX4 Development Kit Lauri Hintsala
2011-12-16 6:07 ` Lauri Hintsala
2011-12-16 6:53 ` Shawn Guo
2011-12-19 7:13 ` Shawn Guo
2011-12-19 7:13 ` Lauri Hintsala
2011-12-19 9:19 ` Shawn Guo
2011-12-19 9:13 ` Russell King - ARM Linux
2011-12-19 9:15 ` Russell King - ARM Linux
2011-12-19 9:32 ` Lauri Hintsala
2011-12-19 9:44 ` Shawn Guo
2011-12-19 11:18 ` Veli-Pekka Peltola
2012-01-04 13:52 ` Shawn Guo
2012-01-04 21:18 ` Russell King - ARM Linux
2012-01-05 11:31 ` Russell King - ARM Linux
2012-01-05 12:15 ` Shawn Guo
2012-01-05 12:08 ` Lauri Hintsala [this message]
2012-03-30 13:13 ` Shawn Guo
2012-03-30 13:15 ` Russell King - ARM Linux
2012-03-30 13:20 ` Russell King - ARM Linux
2012-04-26 7:42 ` Lauri Hintsala
2012-04-26 7:48 ` Shawn Guo
2012-04-26 7:55 ` Lauri Hintsala
2012-03-30 13:22 ` Shawn Guo
2012-03-30 13:28 ` Russell King - ARM Linux
2012-03-30 22:43 ` Nicolas Pitre
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=4F0592D6.6040108@bluegiga.com \
--to=lauri.hintsala@bluegiga$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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