From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: fix v7-M setup stack location
Date: Mon, 28 Apr 2014 10:00:41 +0200 [thread overview]
Message-ID: <20140428080041.GC28564@pengutronix.de> (raw)
In-Reply-To: <1398103637-22828-1-git-send-email-rabin@rab.in>
Hello,
On Mon, Apr 21, 2014 at 08:07:17PM +0200, Rabin Vincent wrote:
> __v7m_setup_stack currently sits in the .proc.info.init section, and
> thus creates a bogus proc info entry (which by the way matches any
> unknown CPU IDs, due to the entry's mask being 0). Move it out of
> there.
>
> Signed-off-by: Rabin Vincent <rabin@rab.in>
Acked-by: Uwe Kleine-K?nig <u.kleine-koenig@pengutronix.de>
It seems the unpatched code didn't do any harm as long as you boot the
resulting kernel on a v7-M machine. So I'd say it's not a very urgent
fix and getting it in during the next merge window is just fine.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
prev parent reply other threads:[~2014-04-28 8:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-21 18:07 [PATCH] ARM: fix v7-M setup stack location Rabin Vincent
2014-04-28 8:00 ` Uwe Kleine-König [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=20140428080041.GC28564@pengutronix.de \
--to=u.kleine-koenig@pengutronix.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).