From: Rusty Russell <rusty@ozlabs.org>
To: Stephen Boyd <sboyd@codeaurora.org>, Joe Perches <joe@perches.com>
Cc: xen-devel@lists.xensource.com,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Greg Kroah-Hartman <gregkh@suse.de>,
Miche Baker-Harvey <miche@google.com>,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
Christian Borntraeger <borntraeger@de.ibm.com>,
Hendrik Brueckner <brueckner@linux.vnet.ibm.com>,
Anton Blanchard <anton@samba.org>,
Amit Shah <amit.shah@redhat.com>
Subject: Re: [PATCH] VirtioConsole support.
Date: Thu, 03 Nov 2011 08:32:13 +1030 [thread overview]
Message-ID: <87k47itc7u.fsf@rustcorp.com.au> (raw)
In-Reply-To: <4EAAF23C.8050102@codeaurora.org>
On Fri, 28 Oct 2011 11:19:40 -0700, Stephen Boyd <sboyd@codeaurora.org> wrote:
> Even better would be kmemdup().
OK, this driver is horribly unloved, and ugly. Noone claims to really
understand it, but people keep poking it.
Ben, Christian, can you figure out what's going on? Is it time for a
complete rewrite?
Thanks,
Rusty.
next prev parent reply other threads:[~2011-11-02 22:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20111027173527.GA23839@phenom.dumpdata.com>
2011-10-27 18:39 ` [PATCH] VirtioConsole support Miche Baker-Harvey
[not found] ` <1319740793-2187-1-git-send-email-miche@google.com>
2011-10-27 21:15 ` Konrad Rzeszutek Wilk
2011-10-31 9:55 ` Amit Shah
2011-10-27 21:43 ` Miche Baker-Harvey
[not found] ` <1319751802-27013-1-git-send-email-miche@google.com>
2011-10-27 21:55 ` Konrad Rzeszutek Wilk
2011-10-28 16:27 ` Greg KH
2011-10-28 2:55 ` Joe Perches
2011-10-28 18:19 ` Stephen Boyd
[not found] ` <4EAAF23C.8050102@codeaurora.org>
2011-11-02 22:02 ` Rusty Russell [this message]
2011-11-03 12:38 ` Christian Borntraeger
2011-11-03 14:15 ` Konrad Rzeszutek Wilk
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=87k47itc7u.fsf@rustcorp.com.au \
--to=rusty@ozlabs.org \
--cc=amit.shah@redhat.com \
--cc=anton@samba.org \
--cc=benh@kernel.crashing.org \
--cc=borntraeger@de.ibm.com \
--cc=brueckner@linux.vnet.ibm.com \
--cc=gregkh@suse.de \
--cc=joe@perches.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miche@google.com \
--cc=sboyd@codeaurora.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=xen-devel@lists.xensource.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;
as well as URLs for NNTP newsgroup(s).