[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <bed54c06-eb00-e682-8a50-236ebb9c1db4@deltatee.com>
Date: Tue, 18 Apr 2017 09:59:09 -0600
From: Logan Gunthorpe <logang@...tatee.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
Cc: David Laight <David.Laight@...LAB.COM>,
xen-devel@...ts.xensource.com, Christoph Hellwig <hch@....de>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
Sagi Grimberg <sagi@...mberg.me>, Jens Axboe <axboe@...nel.dk>,
Tejun Heo <tj@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Dan Williams <dan.j.williams@...el.com>,
Ross Zwisler <ross.zwisler@...ux.intel.com>,
Matthew Wilcox <mawilcox@...rosoft.com>,
Sumit Semwal <sumit.semwal@...aro.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-crypto@...r.kernel.org" <linux-crypto@...r.kernel.org>,
"linux-media@...r.kernel.org" <linux-media@...r.kernel.org>,
"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
"intel-gfx@...ts.freedesktop.org" <intel-gfx@...ts.freedesktop.org>,
"linux-raid@...r.kernel.org" <linux-raid@...r.kernel.org>,
"linux-mmc@...r.kernel.org" <linux-mmc@...r.kernel.org>,
"linux-nvme@...ts.infradead.org" <linux-nvme@...ts.infradead.org>,
"linux-nvdimm@...ts.01.org" <linux-nvdimm@...1.01.org>,
"linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
"open-iscsi@...glegroups.com" <open-iscsi@...glegroups.com>,
"megaraidlinux.pdl@...adcom.com" <megaraidlinux.pdl@...adcom.com>,
"sparmaintainer@...sys.com" <sparmaintainer@...sys.com>,
"devel@...verdev.osuosl.org" <devel@...verdev.osuosl.org>,
"target-devel@...r.kernel.org" <target-devel@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
"rds-devel@....oracle.com" <rds-devel@....oracle.com>,
Steve Wise <swise@...ngridcomputing.com>
Subject: Re: [PATCH 16/22] xen-blkfront: Make use of the new sg_map helper
function
On 18/04/17 09:50 AM, Konrad Rzeszutek Wilk wrote:
> I am not sure if you know, but you can add on each patch the respective
> maintainer via 'CC'. That way you can have certain maintainers CCed only
> on the subsystems they cover. You put it after (or before) your SoB and
> git send-email happilly picks it up.
Yes, but I've seen some maintainers complain when they receive a patch
with no context (ie. cover letter and first patch). So I chose to do it
this way. I expect in this situation, no matter what you do, someone is
going to complain about the approach chosen.
Thanks anyway for the tip.
Logan
Powered by blists - more mailing lists