From: Rob Landley <rob@landley.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux-sh list <linux-sh@vger.kernel.org>,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>
Subject: Re: Commit 594cc251fdd0 (user_access_begin does access_ok) made arch/sh stop booting on qemu.
Date: Thu, 31 Jan 2019 06:42:18 -0600 [thread overview]
Message-ID: <77f57f50-4460-8997-756a-6d6f45504cb5@landley.net> (raw)
In-Reply-To: <CAHk-=wgTxAaviY-WuOKtAd8f4XpE7WF43aaO8F9-CgyowyxSfA@mail.gmail.com>
On 1/31/19 2:30 AM, Linus Torvalds wrote:
> See
>
>
> https://lore.kernel.org/lkml/CAHk-=wiHe4dNHKpE4oGhwwmy23jNTuuFQAgWTGCjjxyOVYjG_w@mail.gmail.com/
>
> for an explanation of the SH bug.
>
> But Guenter Roeck confirmed that my patch fixed it on SH for him. Is there
> something else going on in your configuration?
That fixed it for me.
Thanks,
Rob
prev parent reply other threads:[~2019-01-31 12:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 6:29 Commit 594cc251fdd0 (user_access_begin does access_ok) made arch/sh stop booting on qemu Rob Landley
[not found] ` <CAHk-=wgTxAaviY-WuOKtAd8f4XpE7WF43aaO8F9-CgyowyxSfA@mail.gmail.com>
2019-01-31 12:42 ` Rob Landley [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=77f57f50-4460-8997-756a-6d6f45504cb5@landley.net \
--to=rob@landley.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=torvalds@linux-foundation.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).