From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: mxs: Fix the RTC compatible prop on M28EVK
Date: Tue, 22 Jul 2014 04:11:58 +0200 [thread overview]
Message-ID: <201407220411.58127.marex@denx.de> (raw)
In-Reply-To: <20140221033102.GS3010@S2101-09.ap.freescale.net>
On Friday, February 21, 2014 at 04:31:06 AM, Shawn Guo wrote:
> On Fri, Feb 21, 2014 at 04:14:00AM +0100, Marek Vasut wrote:
> > On Friday, February 21, 2014 at 03:09:16 AM, Shawn Guo wrote:
> > > On Thu, Feb 20, 2014 at 01:31:37PM +0100, Marek Vasut wrote:
> > > > On Friday, January 24, 2014 at 12:23:36 AM, Marek Vasut wrote:
> > > > > The compatible property should be m41t62, not mt41t62, so fix this.
> > > > >
> > > > > Signed-off-by: Marek Vasut <marex@denx.de>
> > > > > Cc: Shawn Guo <shawn.guo@linaro.org>
> > > >
> > > > Bump ?
> > >
> > > Applied. Sorry for the delay.
> >
> > Sure, no problem. Thanks. Shall I submit this for -stable too ?
>
> Oh, at this time which already passes -rc3, I didn't categorize it as a
> critical fix (build error, kernel dumps, system hang) that we should
> send right away for 3.14 and -stable. If you do, you can try to resend
> it to arm-soc folks with my ACK.
Is there anything special to get this into 3.14-stable now or shall I just
follow the general stable submission guidelines ?
Best regards,
Marek Vasut
next prev parent reply other threads:[~2014-07-22 2:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 23:23 [PATCH] ARM: dts: mxs: Fix the RTC compatible prop on M28EVK Marek Vasut
2014-02-20 12:31 ` Marek Vasut
2014-02-21 2:09 ` Shawn Guo
2014-02-21 3:14 ` Marek Vasut
2014-02-21 3:31 ` Shawn Guo
2014-02-24 18:02 ` Marek Vasut
2014-07-22 2:11 ` Marek Vasut [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-07-24 2:08 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=201407220411.58127.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.