From: Wanlong Gao <gaowanlong@cn.fujitsu.com>
To: Andrew Lutomirski <luto@mit.edu>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
werner <w.landgraf@ru.ru>,
linux-kernel@vger.kernel.org
Subject: Re: 3.1-rc6 boot problem reason searching
Date: Fri, 16 Sep 2011 09:33:57 +0800 [thread overview]
Message-ID: <4E72A785.2050207@cn.fujitsu.com> (raw)
In-Reply-To: <CAObL_7EuUyeJ2ebhMhYgY_4O+wUE-rHbc4aBvEKaGrimxU_z7A@mail.gmail.com>
On 09/16/2011 09:27 AM, Andrew Lutomirski wrote:
> 2011/9/15 Linus Torvalds<torvalds@linux-foundation.org>:
>> On Thu, Sep 15, 2011 at 6:10 PM, werner<w.landgraf@ru.ru> wrote:
>>> Meanwhile 3.1-rc6 with the patch by L.T. is compiled, and it boots, with the
>>> original allyesconfig with M486 , so that insofar that problem is resolved.
>>> So that 95% of the population of poorer parts of the world (which have 486
>>> computers) continue to be benefited also by version 3.1 .
>>
>> Thanks for testing.. I suspect you're the only one who ever actually
>> builds i486 kernels any more - at least development kernels ;)
>
> Would you prefer for me to test your patch or to submit my one-liner?
>
> --Andy
Andy:
Please see commit a7f934d4f16144cb9521b62e9b8c9ac0118097da
Thanks
-Wanlong
>
>>
>> Linus
>>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2011-09-16 1:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <web-606439650@zbackend1.aha.ru>
[not found] ` <CA+55aFwyC7s=YK10Wkpr+GzdukXp-JUtf_=MgWcrhBOtTg4eTg@mail.gmail.com>
2011-09-15 2:42 ` 3.1-rc6 boot problem reason searching werner
2011-09-15 3:11 ` Linus Torvalds
2011-09-15 4:11 ` werner
2011-09-15 14:41 ` Andrew Lutomirski
2011-09-15 15:21 ` Andrew Lutomirski
2011-09-15 15:47 ` Linus Torvalds
[not found] ` <web-607296211@zbackend1.aha.ru>
[not found] ` <CAObL_7HAxg0j3ywpTy1-5Y5vBBQLSTiF7AZ0bctRsPOLKA8ZNA@mail.gmail.com>
[not found] ` <CA+55aFwEKNEN8QPpBhAkDQ4UGFtSDtpdwFRSkTvnhaYRTmrsOA@mail.gmail.com>
[not found] ` <CAObL_7Gjk91MFSwbaMnfdxwrM0mDGxWtDBaKMoimg2FSUqjAUg@mail.gmail.com>
[not found] ` <CA+55aFxmW7rFEpanD-ngB-Egx5j1q8b_u31Keo3+s-TJ13UZGA@mail.gmail.com>
2011-09-15 18:23 ` Linus Torvalds
2011-09-15 18:56 ` Andrew Lutomirski
2011-09-16 1:10 ` werner
2011-09-16 1:20 ` Linus Torvalds
2011-09-16 1:27 ` Andrew Lutomirski
2011-09-16 1:33 ` Wanlong Gao [this message]
2011-09-16 1:34 ` Linus Torvalds
2011-09-15 4:28 werner
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=4E72A785.2050207@cn.fujitsu.com \
--to=gaowanlong@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@mit.edu \
--cc=torvalds@linux-foundation.org \
--cc=w.landgraf@ru.ru \
/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