From: Boris Ostrovsky <boris.ostrovsky@oracle•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
Stefano Stabellini <sstabellini@kernel•org>
Cc: Jeremy Fitzhardinge <jeremy@goop•org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle•com>,
Xen Devel <Xen-devel@lists•xensource.com>,
Jens Axboe <axboe@kernel•dk>,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Jan Beulich <JBeulich@suse•com>,
Mike Christie <mchristi@redhat•com>,
david.vrabel@citrix•com, Juergen Gross <jgross@suse•com>
Subject: Re: linux-next: manual merge of the xen-tip tree with the block tree
Date: Mon, 25 Jul 2016 18:25:00 -0400 [thread overview]
Message-ID: <aac9ff10-ae0c-77fa-b1f1-dc12beafd8e6@oracle.com> (raw)
In-Reply-To: <20160726081942.60487736@canb.auug.org.au>
On 07/25/2016 06:19 PM, Stephen Rothwell wrote:
> Hi Stefano,
>
> On Mon, 25 Jul 2016 10:29:11 -0700 (PDT) Stefano Stabellini <sstabellini@kernel•org> wrote:
>> The To and CC list for these emails is a bit outdated. I want to make
>> sure they reach the right people. Could you please add:
>>
>> boris.ostrovsky@oracle•com
>> david.vrabel@citrix•com
> OK, I have added them as contacts for the xen-tip tree. The complete list is now:
>
> Jeremy Fitzhardinge <jeremy@goop•org>
Jeremy is no longer involved with Xen. However,
Juergen Gross <jgross@suse•com>
is also Linux Xen/x86 maintainer.
-boris
> Konrad Rzeszutek Wilk <konrad.wilk@oracle•com>
> Stefano Stabellini <sstabellini@kernel•org>
> <boris.ostrovsky@oracle•com>
> <david.vrabel@citrix•com>
> Xen Devel <Xen-devel@lists•xensource.com>
>
> Please let me know if you need further changes.
>
next prev parent reply other threads:[~2016-07-25 22:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-24 6:14 linux-next: manual merge of the xen-tip tree with the block tree Stephen Rothwell
2016-07-25 17:29 ` Stefano Stabellini
2016-07-25 22:19 ` Stephen Rothwell
2016-07-25 22:22 ` Stefano Stabellini
2016-07-25 22:25 ` Boris Ostrovsky [this message]
2016-07-26 4:57 ` Stephen Rothwell
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=aac9ff10-ae0c-77fa-b1f1-dc12beafd8e6@oracle.com \
--to=boris.ostrovsky@oracle$(echo .)com \
--cc=JBeulich@suse$(echo .)com \
--cc=Xen-devel@lists$(echo .)xensource.com \
--cc=axboe@kernel$(echo .)dk \
--cc=david.vrabel@citrix$(echo .)com \
--cc=jeremy@goop$(echo .)org \
--cc=jgross@suse$(echo .)com \
--cc=konrad.wilk@oracle$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mchristi@redhat$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=sstabellini@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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