From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Daniel Kiper <dkiper@net-space.pl>
Cc: xen-devel@lists.xensource.com
Subject: Re: Patches that are going to be proposed for 2.6.40.
Date: Thu, 12 May 2011 14:53:23 -0400 [thread overview]
Message-ID: <20110512185323.GC24799@dumpdata.com> (raw)
In-Reply-To: <20110512104522.GB27851@router-fw-old.local.net-space.pl>
> > > Additionally, today I am going to prapare final version of memory hotplug
.. snip..
> I posted fix for git commit 24bdb0b62cc82120924762ae6bc85afc8c3f2b26
> yesterday. However, I would like to wait to final version of prerequisite
> patches (David Rientjes sent me some comments yesterday) before publishing
> final version of memory hotplug patch. What time constraints we have
> for memory hotplug now ???
I think the merge window is June 2nd - which means you need to post the
code at least two weeks before that. Your code all looked great and
you can stick my 'Reviewed-by' on the non-Xen code. For the balloon code
the only thing I want is in the git commit and in the source code
a tiny explanation on how a user would 'online' memory using SysFS. You
put that in, you can stick my 'Acked-by' on that code.
Since it is touching mm, I think you need to email the whole patchset to akpm.
Email it to him and CC everybody involved.
>
> > > 2.6.39, however, as I know it could be very difficult to do that
> > > at that stage.
> >
> > We can do it through the stable tree when 2.6.39 gets released.
>
> OK.
stuck it in stable/e820.bugfixes branch. Thanks for posting it.
>
> Daniel
prev parent reply other threads:[~2011-05-12 18:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 17:19 Patches that are going to be proposed for 2.6.40 Konrad Rzeszutek Wilk
2011-05-11 7:42 ` Ian Campbell
2011-05-11 13:14 ` Konrad Rzeszutek Wilk
2011-05-11 15:04 ` Ian Campbell
2011-05-11 9:49 ` Daniel Kiper
2011-05-11 13:17 ` Konrad Rzeszutek Wilk
2011-05-12 10:45 ` Daniel Kiper
2011-05-12 18:53 ` 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=20110512185323.GC24799@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=dkiper@net-space.pl \
--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).