From: Daniel Stodden <daniel.stodden@citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Ian Campbell <Ian.Campbell@eu.citrix.com>,
Jeremy Fitzhardinge <jeremy@goop.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Tom Goetz <tom.goetz@virtualcomputer.com>
Subject: Re: Merging xen/dom0/backend/blktap2 ..
Date: Tue, 15 Mar 2011 17:43:21 -0700 [thread overview]
Message-ID: <1300236201.19837.3.camel@agari.van.xensource.com> (raw)
In-Reply-To: <1300223054.4010.295.camel@agari.van.xensource.com>
On Tue, 2011-03-15 at 17:04 -0400, Daniel Stodden wrote:
> >
> > Can you make a different branch (or just send me the git commit)
> > for the one that touches mm/memory.c?
>
> That's the initial one: 7ccd87f. You could strip that but it's not going
> to build as a module before that ref is gone. It might go at some point.
Oh. Update: I just noticed there's zap_vma_ptes now. So scratch that.
Amazing, always thought I'd eventually have to tear down vmas.
Cheers,
Daniel
next prev parent reply other threads:[~2011-03-16 0:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-10 3:33 Merging xen/dom0/backend/blktap2 Daniel Stodden
2011-03-10 8:31 ` Ian Campbell
2011-03-10 10:39 ` Daniel Stodden
2011-03-10 18:24 ` Konrad Rzeszutek Wilk
2011-03-10 21:57 ` Daniel Stodden
2011-03-11 19:35 ` Konrad Rzeszutek Wilk
2011-03-11 22:02 ` Daniel Stodden
2011-03-15 12:44 ` Daniel Stodden
2011-03-15 19:53 ` Konrad Rzeszutek Wilk
2011-03-15 21:04 ` Daniel Stodden
2011-03-16 0:43 ` Daniel Stodden [this message]
2011-03-16 0:50 ` Daniel Stodden
2011-03-16 3:02 ` Konrad Rzeszutek Wilk
2011-03-19 23:20 ` Daniel Stodden
2011-03-20 20:28 ` Konrad Rzeszutek Wilk
2011-03-21 1:05 ` Daniel Stodden
2011-03-22 16:59 ` Konrad Rzeszutek Wilk
2011-03-22 19:17 ` Daniel Stodden
[not found] <4d791af5.493cdc0a.174a.ffff9bfeSMTPIN_ADDED@mx.google.com>
2011-03-14 12:29 ` Thomas Goetz
2011-03-14 21:05 ` Daniel Stodden
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=1300236201.19837.3.camel@agari.van.xensource.com \
--to=daniel.stodden@citrix.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--cc=tom.goetz@virtualcomputer.com \
--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).