From: Bruno Wolff III <bruno@wolff.to>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Jean Delvare <khali@linux-fr.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Jingoo Han <jg1.han@samsung.com>,
linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] kernel: replace strict_strto*() with kstrto*()
Date: Fri, 27 Sep 2013 19:09:51 -0500 [thread overview]
Message-ID: <20130928000951.GA7019@wolff.to> (raw)
In-Reply-To: <20130927131820.7fc04051.akpm@linux-foundation.org>
On Fri, Sep 27, 2013 at 13:18:20 -0700,
Andrew Morton <akpm@linux-foundation.org> wrote:
>On Fri, 27 Sep 2013 19:53:53 +0200 Jean Delvare <khali@linux-fr.org> wrote:
>
>> Andrew,
>>
>> On Fri, 27 Sep 2013 09:50:39 -0600, Bjorn Helgaas wrote:
>> > There's some indication that this change might have broken handling of
>> > signed types. See
>> > https://lists.ozlabs.org/pipermail/linuxppc-dev/2013-September/111758.html
>> > and https://bugzilla.kernel.org/show_bug.cgi?id=61811.
>>
>> It seems this is hurting more users than I would have expected, and
>> people are spending significant amounts of time to figure out what the
>> root cause to their problem is. May I suggest that my fix should find
>> its way to Linus' tree rather sooner than later?
>>
>
>Done. I had to send that one by hand as I'm not at my desk...
I just did a successful test of the patch from the mailing list. So it at
least solved the problem in my case.
prev parent reply other threads:[~2013-09-28 0:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 8:39 [PATCH] kernel: replace strict_strto*() with kstrto*() Jingoo Han
2013-09-27 15:50 ` Bjorn Helgaas
2013-09-27 17:53 ` Jean Delvare
2013-09-27 20:18 ` Andrew Morton
2013-09-28 0:09 ` Bruno Wolff III [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=20130928000951.GA7019@wolff.to \
--to=bruno@wolff.to \
--cc=akpm@linux-foundation.org \
--cc=bhelgaas@google.com \
--cc=jg1.han@samsung.com \
--cc=khali@linux-fr.org \
--cc=linux-kernel@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