public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Luis R. Rodriguez" <mcgrof@suse.com>
Cc: David Rientjes <rientjes@google.com>,
	Michal Marek <mmarek@suse.cz>, Paul Bolle <pebolle@tiscali.nl>,
	Julien Grall <julien.grall@linaro.org>,
	kvm@vger.kernel.org,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	x86@kernel.org, josh@joshtriplett.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	David Vrabel <david.vrabel@citrix.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	xen-devel@lists.xenproject.org,
	Andrew Morton <akpm@linux-foundation.org>,
	sam@ravnborg.org, Benjamin Poirier <bpoirier@suse.de>
Subject: Re: [Xen-devel] [PATCH v3 0/2] x86/arm64: add xenconfig
Date: Wed, 25 Feb 2015 16:44:20 -0500	[thread overview]
Message-ID: <20150225214420.GB314@l.oracle.com> (raw)
In-Reply-To: <CAB=NE6UM-Co37sZQFjh9J7h1N7eXp-AnuZTogUy88rPnLQ5i9A@mail.gmail.com>

On Wed, Feb 25, 2015 at 01:25:59PM -0800, Luis R. Rodriguez wrote:
> On Wed, Feb 25, 2015 at 1:19 PM, Konrad Rzeszutek Wilk
> <konrad.wilk@oracle.com> wrote:
> > On Wed, Feb 25, 2015 at 01:11:04PM -0800, David Rientjes wrote:
> >> On Wed, 25 Feb 2015, Luis R. Rodriguez wrote:
> >>
> >> > I am reworking Xen's kconfig stuff right now, so perhaps what is best
> >> > is for this series to be folded under those changes and I'd submit
> >> > them as the last series in the changes. That would avoid collateral
> >> > changes as I revamp tons of Xen kconfig things. This would then go
> >> > under David Vrabel's tree, but since it involves x86 stuff its unclear
> >> > if its OK for that -- I think so? Let me know.
> >> >
> >>
> >> Ok, sounds good, and I agree it would be better to hold off on doing this
> >> if there are going to be substantial changes to the config options later.
> >> I think once the x86 bits get an ack from one of the x86 guys that you
> >> should be good to go!
> >
> > Ingo (x86 guys) mentioned in one of his emails that he glosses over
> > emails if they say 'xen'.
> 
> Then this should be able to go through David Vrabel no, as he does care.

:-)
> 
> > Perhaps you need to change the title to be more catchy?
> 
> If folks don't want to deal with Xen patches it should be fine, but we
> do need a route upstream, this seems to make sense to go through David
> Vrabel in the future no?

Yes, any of the Xen maintainers (me, David, or Boris).

> 
>  Luis

      reply	other threads:[~2015-02-25 21:44 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-14 19:33 [PATCH v3 0/2] x86/arm64: add xenconfig Luis R. Rodriguez
2015-01-14 19:33 ` [PATCH v3 1/2] x86, platform, xen, kconfig: clarify kvmconfig is for kvm Luis R. Rodriguez
2015-01-14 19:33 ` [PATCH v3 2/2] x86, arm, platform, xen, kconfig: add xen defconfig helper Luis R. Rodriguez
2015-01-15 10:47   ` Stefano Stabellini
2015-01-23  0:34 ` [PATCH v3 0/2] x86/arm64: add xenconfig Luis R. Rodriguez
2015-01-23 15:19   ` Stefano Stabellini
2015-01-27 20:00     ` Luis R. Rodriguez
2015-01-29 20:38       ` Luis R. Rodriguez
2015-01-29 20:47         ` Paul Bolle
2015-01-30 10:49           ` Michal Marek
2015-01-30 18:25             ` Luis R. Rodriguez
2015-02-02 21:13               ` Michal Marek
2015-02-02 21:32                 ` Luis R. Rodriguez
2015-02-07  0:08                   ` Luis R. Rodriguez
2015-02-10 22:21                     ` David Rientjes
2015-02-10 22:32                       ` Paul Bolle
2015-02-25 15:44                         ` Michal Marek
2015-02-25 20:49                           ` David Rientjes
2015-02-25 21:05                             ` [Xen-devel] " Luis R. Rodriguez
2015-02-25 21:11                               ` David Rientjes
2015-02-25 21:19                                 ` Konrad Rzeszutek Wilk
2015-02-25 21:25                                   ` Luis R. Rodriguez
2015-02-25 21:44                                     ` 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=20150225214420.GB314@l.oracle.com \
    --to=konrad.wilk@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=bpoirier@suse.de \
    --cc=david.vrabel@citrix.com \
    --cc=hpa@zytor.com \
    --cc=josh@joshtriplett.org \
    --cc=julien.grall@linaro.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@suse.com \
    --cc=mmarek@suse.cz \
    --cc=pebolle@tiscali.nl \
    --cc=rientjes@google.com \
    --cc=sam@ravnborg.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=x86@kernel.org \
    --cc=xen-devel@lists.xenproject.org \
    /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