From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Juergen Gross <JGross@suse.com>,
Xiao Guangrong <guangrong.xiao@linux.intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Arnd Bergmann <arnd@arndb.de>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@ml01.01.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Stefano Stabellini <stefano@aporeto.com>,
David Vrabel <david.vrabel@citrix.com>,
Jan Beulich <jbeulich@suse.com>,
xen-devel@lists.xenproject.org,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [Xen-devel] [RFC KERNEL PATCH 0/2] Add Dom0 NVDIMM support for Xen
Date: Tue, 11 Oct 2016 15:43:38 -0400 [thread overview]
Message-ID: <20161011194338.GB25907@localhost.localdomain> (raw)
In-Reply-To: <20161011184215.GB23193@localhost.localdomain>
> Andrew, why are you providing input to this so late?
First of sorry for this outburst. It was quite uncalled for and quite
unprofessional. You of all people have so much on your plate that I am
astonished that you are able to operate with some many pokers in the
fire.
Again, my sincere apology.
next prev parent reply other threads:[~2016-10-11 19:47 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-10 0:35 [RFC KERNEL PATCH 0/2] Add Dom0 NVDIMM support for Xen Haozhong Zhang
2016-10-10 0:35 ` [RFC KERNEL PATCH 1/2] nvdimm: add PFN_MODE_XEN to pfn device for Xen usage Haozhong Zhang
2016-10-10 0:35 ` [RFC KERNEL PATCH 2/2] xen, nvdimm: report pfn devices in PFN_MODE_XEN to Xen hypervisor Haozhong Zhang
2016-10-10 3:45 ` [RFC KERNEL PATCH 0/2] Add Dom0 NVDIMM support for Xen Dan Williams
2016-10-10 6:32 ` Haozhong Zhang
2016-10-10 16:24 ` Dan Williams
2016-10-11 7:11 ` Haozhong Zhang
2016-10-10 16:43 ` [Xen-devel] " Andrew Cooper
2016-10-11 5:52 ` Haozhong Zhang
2016-10-11 18:37 ` Andrew Cooper
2016-10-11 18:45 ` Konrad Rzeszutek Wilk
2016-10-11 18:48 ` Konrad Rzeszutek Wilk
2016-10-11 13:08 ` Jan Beulich
2016-10-11 15:53 ` Dan Williams
2016-10-11 16:58 ` Konrad Rzeszutek Wilk
2016-10-11 17:51 ` Dan Williams
2016-10-11 18:15 ` Andrew Cooper
2016-10-11 18:42 ` Konrad Rzeszutek Wilk
2016-10-11 19:43 ` Konrad Rzeszutek Wilk [this message]
2016-10-11 18:33 ` Konrad Rzeszutek Wilk
2016-10-11 19:28 ` Dan Williams
2016-10-11 19:48 ` Konrad Rzeszutek Wilk
2016-10-11 20:17 ` Dan Williams
2016-10-12 10:33 ` Haozhong Zhang
2016-10-12 11:32 ` Jan Beulich
2016-10-12 14:58 ` Haozhong Zhang
2016-10-12 15:39 ` Jan Beulich
2016-10-12 15:42 ` Dan Williams
2016-10-12 16:01 ` Jan Beulich
2016-10-12 16:19 ` Dan Williams
2016-10-13 8:34 ` Jan Beulich
2016-10-13 8:53 ` Haozhong Zhang
2016-10-13 9:08 ` Jan Beulich
2016-10-13 15:40 ` Dan Williams
2016-10-13 16:01 ` Andrew Cooper
2016-10-13 18:59 ` Dan Williams
2016-10-13 19:33 ` Andrew Cooper
2016-10-14 7:08 ` Haozhong Zhang
2016-10-14 12:18 ` Andrew Cooper
2016-10-20 9:14 ` Haozhong Zhang
2016-10-20 21:46 ` Andrew Cooper
2016-10-14 10:03 ` Jan Beulich
2016-10-13 15:46 ` Haozhong Zhang
2016-10-14 10:16 ` Jan Beulich
2016-10-20 9:15 ` Haozhong Zhang
2016-10-13 9:08 ` Haozhong Zhang
2016-10-11 20:18 ` Andrew Cooper
2016-10-12 7:25 ` Jan Beulich
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=20161011194338.GB25907@localhost.localdomain \
--to=konrad.wilk@oracle.com \
--cc=JGross@suse.com \
--cc=akpm@linux-foundation.org \
--cc=andrew.cooper3@citrix.com \
--cc=arnd@arndb.de \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=guangrong.xiao@linux.intel.com \
--cc=jbeulich@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@ml01.01.org \
--cc=stefano@aporeto.com \
--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