From: Boaz Harrosh <bharrosh@panasas.com>
To: Amerigo Wang <xiyou.wangcong@gmail.com>
Cc: Paul Menage <menage@google.com>,
akpm@linux-foundation.org, jdike@addtoit.com,
user-mode-linux-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [uml-devel] [PATCH] UML: Fix some apparent bitrot
Date: Wed, 24 Jun 2009 15:23:02 +0300 [thread overview]
Message-ID: <4A421AA6.5060908@panasas.com> (raw)
In-Reply-To: <20090622024610.GC5893@cr0.nay.redhat.com>
On 06/22/2009 05:46 AM, Amerigo Wang wrote:
> On Fri, Jun 19, 2009 at 05:55:24PM -0700, Paul Menage wrote:
>> UML: Fix some apparent bitrot
>>
>> - migration of net_device methods into net_device_ops
>> - dma_sync_single() changes
>> - cpumask_clear() -> cpumask_clear_cpu()
>>
>> Signed-off-by: Paul Menage <menage@google.com>
>
>
> Looks good.
>
> Acked-by: WANG Cong <xiyou.wangcong@gmail.com>
>
>
Dear Jeff, Amerigo
who is pushing this patch to Linus for 2.6.31. (ASAP)
Linus has threatened to cut -rc1 soon, and it is
unbuildable for UML currently.
Thanks in advance
Boaz
next prev parent reply other threads:[~2009-06-24 12:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-20 0:55 [PATCH] UML: Fix some apparent bitrot Paul Menage
2009-06-22 2:46 ` Amerigo Wang
2009-06-24 12:23 ` Boaz Harrosh [this message]
2009-06-25 10:47 ` [uml-devel] " Amerigo Wang
2009-06-22 8:43 ` Boaz Harrosh
2009-06-22 8:57 ` Amerigo Wang
2009-06-22 10:52 ` Stephen Rothwell
2009-06-22 12:05 ` Boaz Harrosh
2009-06-25 10:49 ` Amerigo Wang
2009-06-25 14:51 ` Jeff Dike
2009-06-26 2:01 ` Stephen Rothwell
2009-06-26 2:48 ` Jeff Dike
2009-06-26 4:15 ` Stephen Rothwell
2009-06-25 3:59 ` Stephen Rothwell
2009-06-25 7:57 ` Boaz Harrosh
2009-06-25 8:06 ` Paul Menage
2009-06-25 8:08 ` Boaz Harrosh
2009-06-25 10:52 ` Amerigo Wang
2009-06-26 1:08 ` Stephen Rothwell
2009-06-26 1:07 ` Stephen Rothwell
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=4A421AA6.5060908@panasas.com \
--to=bharrosh@panasas.com \
--cc=akpm@linux-foundation.org \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=xiyou.wangcong@gmail.com \
/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