From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>, xen-devel@lists.xensource.com
Subject: Re: [GIT] xenbus backend support for upstream
Date: Mon, 13 Dec 2010 09:48:51 -0500 [thread overview]
Message-ID: <20101213144851.GA12648@dumpdata.com> (raw)
In-Reply-To: <1291992235.13966.5018.camel@zakaz.uk.xensource.com>
On Fri, Dec 10, 2010 at 02:43:55PM +0000, Ian Campbell wrote:
> The following git pull request adds the Xenbus infrastructure for Xen
> backend drivers to the upstream 2.6.37-rc kernel. It essentially
> refactors the frontend xenbus scaffolding into frontend and common and
> then adds the backend part.
>
> All but one patch is cherry-picked from xen.git xen/dom0/backend/core.
> It wasn't possible to simply merge the branch because that pulled in a
> bunch of 2.6.32-style dom0 support which conflicts with what is now
> upstream.
>
> The only cherry-picked patch which required changes was the "xen:
> separate out frontend xenbus" commit which needed updating because the
> code which it moves has changed since it was written (primarily the
> changes to wait_for_devices e.g. c6e1971139be, f8dc33088feb,
> ae7888012969).
>
> The last patch is new and fixes up the checkpatch issues in the
> aggregate of the previous commits. I did it this way rather than fixing
> individual patches since I wanted to retain the history as is.
>
> I have a WIP set of changes which port netback onto this infrastructure
> (the port works but still uses PageForeign and hence is not
> upstreamable). I also tested with a merge of
> git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git
> devel/xen-pciback-0.1 and the result seemed functional.
Ok. It compiled for me fine and looks fine. I stuck it on my branch at
linux-next
prev parent reply other threads:[~2010-12-13 14:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-10 14:43 [GIT] xenbus backend support for upstream Ian Campbell
2010-12-13 14:48 ` Konrad Rzeszutek Wilk [this message]
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=20101213144851.GA12648@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Campbell@citrix.com \
--cc=jeremy@goop.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).