From: James Hogan <jhogan@kernel.org>
To: NeilBrown <neil@brown.name>
Cc: John Crispin <john@phrozen.org>,
Ralf Baechle <ralf@linux-mips.org>,
linux-mips@linux-mips.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MIPS: ralink: remove ralink_halt()
Date: Wed, 21 Mar 2018 23:52:50 +0000 [thread overview]
Message-ID: <20180321235249.GC13126@saruman> (raw)
In-Reply-To: <87370v9mkg.fsf@notabene.neil.brown.name>
[-- Attachment #1: Type: text/plain, Size: 1200 bytes --]
On Tue, Mar 20, 2018 at 07:29:51PM +1100, NeilBrown wrote:
>
> ralink_halt() does nothing that machine_halt()
> doesn't already do, so it adds no value.
>
> It actually causes incorrect behaviour due to the
> "unreachable()" at the end. This tell the compiler that the
> end of the function will never be reached, which isn't true.
> The compiler responds by not adding a 'return' instruction,
> so control simply moves on to whatever bytes come afterwards
> in memory. In my tested, that was the ralink_restart()
> function. This means that an attempt to 'halt' the machine
> would actually cause a reboot.
>
> So remove ralink_halt() so that a 'halt' really does halt.
>
> Signed-off-by: NeilBrown <neil@brown.name>
Thanks, I've cosmetically tweaked the commit message (mainly reflow to
72 characters) and added:
Fixes: c06e836ada59 ("MIPS: ralink: adds reset code")
Cc: <stable@vger.kernel.org> # 3.9+
and applied for 4.16.
BTW, I'm intrigued to know if there's a particular reason you don't
author / sign-off as "Neil Brown"? Its supposed to be real names, though
"NeilBrown" is hardly difficult to figure out so I don't actually
object.
Cheers
James
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-03-21 23:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 8:29 [PATCH] MIPS: ralink: remove ralink_halt() NeilBrown
2018-03-21 23:52 ` James Hogan [this message]
2018-03-22 1:34 ` NeilBrown
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=20180321235249.GC13126@saruman \
--to=jhogan@kernel.org \
--cc=john@phrozen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=neil@brown.name \
--cc=ralf@linux-mips.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