From: Michal Marek <mmarek@suse.cz>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
david.vrabel@citrix.com, konrad.wilk@oracle.com,
Ian.Campbell@citrix.com, xen-devel@lists.xenproject.org
Cc: josh@joshtriplett.org, bp@suse.de, penberg@kernel.org,
rientjes@google.com, rdunlap@infradead.org,
levinsasha928@gmail.com, mtosatti@redhat.com,
fengguang.wu@intel.com, yamada.masahiro@socionext.com,
linux-kernel@vger.kernel.org,
"Luis R. Rodriguez" <mcgrof@suse.com>
Subject: Re: [PATCH v6 0/2] kconfig: add xenconfig
Date: Thu, 21 May 2015 16:20:27 +0800 [thread overview]
Message-ID: <555D954B.8010409@suse.cz> (raw)
In-Reply-To: <1432148019-15932-1-git-send-email-mcgrof@do-not-panic.com>
Dne 21.5.2015 v 02:53 Luis R. Rodriguez napsal(a):
> From: "Luis R. Rodriguez" <mcgrof@suse.com>
>
> Michal Marek, Xen folks (David Vrabel, Konrad, Ian), which tree should
> these go through?
Not kbuild, if I may ask :). Otherwise people will find me in
get_maintainer.pl output and keep CCing me on updates to the xen.config
files, which is something I am not at all familiar with.
Michal
next prev parent reply other threads:[~2015-05-21 8:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 18:53 [PATCH v6 0/2] kconfig: add xenconfig Luis R. Rodriguez
2015-05-20 18:53 ` [PATCH v6 1/2] kconfig: clarify kvmconfig is for kvm Luis R. Rodriguez
2015-05-20 18:53 ` [PATCH v6 2/2] kconfig: add xenconfig defconfig helper Luis R. Rodriguez
2015-05-21 14:49 ` Masahiro Yamada
2015-05-21 18:47 ` Luis R. Rodriguez
2015-05-25 1:40 ` Masahiro Yamada
2015-05-21 8:20 ` Michal Marek [this message]
2015-05-21 18:32 ` [PATCH v6 0/2] kconfig: add xenconfig Luis R. Rodriguez
2015-05-28 21:50 ` Luis R. Rodriguez
2015-06-08 23:35 ` Luis R. Rodriguez
2015-06-09 13:44 ` Konrad Rzeszutek Wilk
2015-06-15 19:07 ` Luis R. Rodriguez
2015-06-16 10:10 ` [Xen-devel] " David Vrabel
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=555D954B.8010409@suse.cz \
--to=mmarek@suse.cz \
--cc=Ian.Campbell@citrix.com \
--cc=bp@suse.de \
--cc=david.vrabel@citrix.com \
--cc=fengguang.wu@intel.com \
--cc=josh@joshtriplett.org \
--cc=konrad.wilk@oracle.com \
--cc=levinsasha928@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@do-not-panic.com \
--cc=mcgrof@suse.com \
--cc=mtosatti@redhat.com \
--cc=penberg@kernel.org \
--cc=rdunlap@infradead.org \
--cc=rientjes@google.com \
--cc=xen-devel@lists.xenproject.org \
--cc=yamada.masahiro@socionext.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