From: Frank van der Linden <Frank.Vanderlinden@Sun.COM>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: Gavin Maltby <Gavin.Maltby@Sun.COM>,
Christoph Egger <Christoph.Egger@amd.com>,
xen-devel@lists.xensource.com, "Shan,
Haitao" <haitao.shan@intel.com>
Subject: Re: [PATCH 0/4] CPU online/offline support in Xen
Date: Tue, 09 Sep 2008 13:20:05 -0600 [thread overview]
Message-ID: <48C6CC65.7010307@Sun.COM> (raw)
In-Reply-To: <C4EC0C72.1CF76%keir.fraser@eu.citrix.com>
Keir Fraser wrote:
> You can hardly expect to do work in private and then 'surface the submarine'
> when others post patches and expect them to do the work to merge with you.
> If Intel's patches look acceptable then they will be checked in and Sun will
> have to do the merge work to get any extra enhancements or features in their
> patchset to work on top. That is unless you can see strong reason why Sun's
> patches are technically better.
>
Well, not quite in private, you may remember that I did a presentation
at the Xen Summit.
Anyway, of course there is no point in not accepting or delaying a patch
for something that is not available yet. I'll comment on the submitted
patch, I think I see some issues that we found that aren't addressed in it.
- Frank
next prev parent reply other threads:[~2008-09-09 19:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-09 8:58 [PATCH 0/4] CPU online/offline support in Xen Shan, Haitao
2008-09-09 9:06 ` Christoph Egger
2008-09-09 9:08 ` Shan, Haitao
2008-09-09 10:20 ` Keir Fraser
2008-09-09 10:35 ` Gavin Maltby
2008-09-09 10:48 ` Keir Fraser
2008-09-09 19:20 ` Frank van der Linden [this message]
2008-09-09 19:31 ` Keir Fraser
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=48C6CC65.7010307@Sun.COM \
--to=frank.vanderlinden@sun.com \
--cc=Christoph.Egger@amd.com \
--cc=Gavin.Maltby@Sun.COM \
--cc=haitao.shan@intel.com \
--cc=keir.fraser@eu.citrix.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 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.