From: Luca Bigliardi <shammash@artha.org>
To: "Américo Wang" <xiyou.wangcong@gmail.com>
Cc: Jiri Kosina <jkosina@suse.cz>,
trivial@kernel.org, linux-kernel@vger.kernel.org,
jdike@addtoit.com, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] Fix vde network backend in user mode linux
Date: Mon, 16 Feb 2009 14:23:45 +0100 [thread overview]
Message-ID: <20090216132344.GN24031@pintsize> (raw)
In-Reply-To: <20090216124939.GC23665@hack.private>
On Mon, Feb 16, 2009 at 08:49 PM, Américo Wang wrote:
> On Mon, Feb 16, 2009 at 01:38:46PM +0100, Jiri Kosina wrote:
> >
> >[ doesn't seem to be picked up by anyone into current -next nor -mmotm,
> > but isn't appropriate for trivial; adding akpm to cc ]
> >
> >On Mon, 2 Feb 2009, Luca Bigliardi wrote:
> >
> >> * Replace kmalloc() with uml_kmalloc()
> >> (fix build failure)
>
>
> Weird... I sent a patch for this several months ago! I thought
> Jeff had already taken it... No?
I did as well (in June/July 08 IIRC) through usermodelinux-devel mailing
list but the patch didn't hit, so this time I've tried this way.
> >> * Remove unnecessary UM_KERN_INFO in printk()
> >> (don't display '<6>' while printing info)
>
> But why only this one, not other UM_KERN_INFO in the same file?
Other lines are preceded by a 'new_text_line' so vprintk 'eats' the token.
Thank you,
luca
--
Beware of programmers who carry screwdrivers.
-- Leonard Brandwein
http://shammash.homelinux.org/ - http://www.artha.org/ - http://www.yue.it/
next prev parent reply other threads:[~2009-02-16 13:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-02 17:28 [PATCH] Fix vde network backend in user mode linux Luca Bigliardi
2009-02-11 13:02 ` Jiri Kosina
2009-02-16 12:38 ` Jiri Kosina
2009-02-16 12:49 ` Américo Wang
2009-02-16 12:51 ` Jiri Kosina
2009-02-16 13:21 ` Américo Wang
2009-02-16 13:23 ` Luca Bigliardi [this message]
2009-02-17 13:07 ` Américo Wang
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=20090216132344.GN24031@pintsize \
--to=shammash@artha.org \
--cc=akpm@linux-foundation.org \
--cc=jdike@addtoit.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@kernel.org \
--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 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.