From: "Michael Büsch" <m@bues.ch>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org,
Ilia Mirkin <imirkin@alum.mit.edu>
Subject: Re: [PATCH] m32r: Fix clearing of thread info fault code
Date: Sat, 21 Nov 2015 15:55:45 +0000 [thread overview]
Message-ID: <20151121165545.14962900@wiggum> (raw)
In-Reply-To: <20151119150832.43f94bdd211e71f9f91c90ae@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 542 bytes --]
On Thu, 19 Nov 2015 15:08:32 -0800
Andrew Morton <akpm@linux-foundation.org> wrote:
> I don't think we should apply this unless someone can runtime test it.
> Presumably the current code works OK, but we just don't know what
> nasties the fixed version might expose.
I fully agree. But who can test it?
> The best I can think of is to put a big FIXME comment in there, so
> perhaps one day if someone is working on m32r stuff, they may try
> fixing it.
Or remove the architecture, if nobody is using it? :)
--
Michael
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: "Michael Büsch" <m@bues.ch>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org,
Ilia Mirkin <imirkin@alum.mit.edu>
Subject: Re: [PATCH] m32r: Fix clearing of thread info fault code
Date: Sat, 21 Nov 2015 16:55:45 +0100 [thread overview]
Message-ID: <20151121165545.14962900@wiggum> (raw)
In-Reply-To: <20151119150832.43f94bdd211e71f9f91c90ae@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 542 bytes --]
On Thu, 19 Nov 2015 15:08:32 -0800
Andrew Morton <akpm@linux-foundation.org> wrote:
> I don't think we should apply this unless someone can runtime test it.
> Presumably the current code works OK, but we just don't know what
> nasties the fixed version might expose.
I fully agree. But who can test it?
> The best I can think of is to put a big FIXME comment in there, so
> perhaps one day if someone is working on m32r stuff, they may try
> fixing it.
Or remove the architecture, if nobody is using it? :)
--
Michael
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-11-21 15:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 18:45 [PATCH] m32r: Fix clearing of thread info fault code Michael Büsch
2015-06-18 18:45 ` Michael Büsch
2015-11-19 20:12 ` Michael Büsch
2015-11-19 20:12 ` Michael Büsch
2015-11-19 20:13 ` Michael Büsch
2015-11-19 20:13 ` Michael Büsch
2015-11-19 23:08 ` Andrew Morton
2015-11-19 23:08 ` Andrew Morton
2015-11-21 15:55 ` Michael Büsch [this message]
2015-11-21 15:55 ` Michael Büsch
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=20151121165545.14962900@wiggum \
--to=m@bues.ch \
--cc=akpm@linux-foundation.org \
--cc=imirkin@alum.mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.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.