From: "H. Peter Anvin" <hpa@zytor.com>
To: Boaz Harrosh <bharrosh@panasas.com>
Cc: "Geert Uytterhoeven" <geert@linux-m68k.org>,
"Borislav Petkov" <bp@alien8.de>,
"Toralf Förster" <toralf.foerster@gmx.de>,
uml-devel <user-mode-linux-devel@lists.sourceforge.net>,
linux-kernel <linux-kernel@vger.kernel.org>,
"Jeff Dike" <jdike@addtoit.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: [uml-devel] [PATCH resend] um, hweight: Fix UML boot crash
Date: Mon, 14 Jun 2010 09:41:51 -0700 [thread overview]
Message-ID: <4C165BCF.4030507@zytor.com> (raw)
In-Reply-To: <4C1653FF.3080108@panasas.com>
On 06/14/2010 09:08 AM, Boaz Harrosh wrote:
> On 06/09/2010 09:29 PM, H. Peter Anvin wrote:
>> On 06/09/2010 01:46 AM, Geert Uytterhoeven wrote:
>>>
>>> Peter, are you happy with this?
>>> Although we still don't know why UML cannot grok it, it does fix a
>>> regression in post-2.6.34.
>>>
>>
>> Yes, I'll push it.
>>
>> -hpa
>
> Peter hi.
>
> Why have we missed that patch from -rc3. This is so *not fun* to keep
> out-of-tree patches. Specially when working with lots of other people's
> trees.
>
> Please push it ASAP
> Boaz
We made the decision of not pushing our queue for -rc3 because Linus
specifically wanted only critical fixes for -rc3. We will push it for
-rc4 for when Linus returns.
Also, you may want to consider moderating your tone.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2010-06-14 16:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-09 8:04 [PATCH resend] um, hweight: Fix UML boot crash Boaz Harrosh
2010-06-09 8:09 ` [uml-devel] " Boaz Harrosh
2010-06-09 8:46 ` Geert Uytterhoeven
2010-06-09 9:08 ` Boaz Harrosh
2010-06-09 9:32 ` Américo Wang
2010-06-09 18:29 ` H. Peter Anvin
2010-06-14 16:08 ` Boaz Harrosh
2010-06-14 16:41 ` H. Peter Anvin [this message]
2010-06-14 18:18 ` Boaz Harrosh
2010-06-09 16:39 ` Boaz Harrosh
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=4C165BCF.4030507@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@linux-foundation.org \
--cc=bharrosh@panasas.com \
--cc=bp@alien8.de \
--cc=geert@linux-m68k.org \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=toralf.foerster@gmx.de \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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