From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: mxs: Update mxs_defconfig
Date: Thu, 17 Jan 2013 02:22:50 +0100 [thread overview]
Message-ID: <201301170222.51048.marex@denx.de> (raw)
In-Reply-To: <20130117012010.GA26179@S2101-09.ap.freescale.net>
Dear Shawn Guo,
> On Tue, Jan 15, 2013 at 05:31:05PM -0200, Fabio Estevam wrote:
> > Shawn,
> >
> > On Tue, Dec 25, 2012 at 11:23 AM, Shawn Guo <shawn.guo@linaro.org> wrote:
> > > Applied with one comment below to Fabio.
> >
> > Which tree this was applied?
>
> Just pushed out branch mxs/soc.
Do you think this can be made a stable matter for 3.7 ? It's a defconfig update
afterall and it help a great deal.
> Shawn
Best regards,
Marek Vasut
next prev parent reply other threads:[~2013-01-17 1:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-21 2:07 [PATCH] arm: mxs: Update mxs_defconfig Marek Vasut
2012-12-25 13:23 ` Shawn Guo
2012-12-25 13:27 ` Fabio Estevam
2013-01-15 19:31 ` Fabio Estevam
2013-01-17 1:20 ` Shawn Guo
2013-01-17 1:22 ` Marek Vasut [this message]
2013-01-17 2:12 ` Shawn Guo
2013-03-03 21:28 ` Marek Vasut
2013-03-04 1:07 ` Shawn Guo
2013-03-04 12:15 ` Marek Vasut
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=201301170222.51048.marex@denx.de \
--to=marex@denx.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;
as well as URLs for NNTP newsgroup(s).