All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hollis Blanchard <hollisb@us.ibm.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: [Patch]: adding physdev_op to hypercall.h
Date: Fri, 10 Mar 2006 11:51:24 -0600	[thread overview]
Message-ID: <4411BC9C.8010406@us.ibm.com> (raw)
In-Reply-To: <6ddde313f15d14b95e7c17294aa1e9a0@cl.cam.ac.uk>

Keir Fraser wrote:
> 
> On 10 Mar 2006, at 16:23, Tristan Gingold wrote:
>> very small patch to prepare comming soon patches on ia64.
> 
> Firstly, it belongs on the ia64-devel list and in the ia64-devel tree.

I'm beginning to split out the arch-neutral changes we've made for PPC 
and intend to submit those individually to xen-devel so that each can be 
discussed as usual. Then once the changes we need are in, we can then 
drop in the whole xen/arch/ppc directory.

With Tristan's patch, which is to arch-neutral code, you seem to prefer 
it be part of the ia64 tree which you'll then pull later. What if you 
don't like some of their changes? Do you give them feedback only after 
they ask you to pull?

In general I assumed that patches that affect arch-neutral code should 
be submitted to xen-devel; is that not the case?

-- 
Hollis Blanchard
IBM Linux Technology Center

  reply	other threads:[~2006-03-10 17:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-10 16:23 [Patch]: adding physdev_op to hypercall.h Tristan Gingold
2006-03-10 16:34 ` Keir Fraser
2006-03-10 17:51   ` Hollis Blanchard [this message]
2006-03-10 17:29 ` Muli Ben-Yehuda
2006-03-13  8:33   ` Tristan Gingold

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=4411BC9C.8010406@us.ibm.com \
    --to=hollisb@us.ibm.com \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --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.