From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Johannes Thumshirn <jthumshirn@suse.de>
Cc: Arvind Yadav <arvind.yadav.cs@gmail.com>,
martin.petersen@oracle.com, jejb@linux.vnet.ibm.com, mdr@sgi.com,
hare@suse.com, aacraid@adaptec.com, matthew@wil.cx,
fthain@telegraphics.com.au, schmitzmic@gmail.com,
kashyap.desai@broadcom.com, sumit.saxena@broadcom.com,
gotom@debian.or.jp, mrochs@linux.vnet.ibm.com,
yokota@netlab.is.tsukuba.ac.jp,
QLogic-Storage-Upstream@cavium.com, jinpu.wang@profitbricks.com,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/29] constify scsi pci_device_id.
Date: Mon, 07 Aug 2017 13:28:18 -0400 [thread overview]
Message-ID: <yq1tw1j9tjh.fsf@oracle.com> (raw)
In-Reply-To: <20170731092753.GB6417@linux-x5ow.site> (Johannes Thumshirn's message of "Mon, 31 Jul 2017 11:27:53 +0200")
Johannes,
> Ultimately it's up to Martin and James but I don't see a hughe benefit
> in having it all in a separate patch.
Generally speaking, I prefer driver maintainers to be able to sign off
on changes to their code. So I tend to lean towards a per-driver
grouping.
However, having a bazillion identical commit messages is also really
annoying. So for automated changes like this, I'd rather just have a
single patch.
It needs to have a really good and comprehensive commit messages that
justifies the (sub) tree-wide change, though...
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2017-08-07 17:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-30 8:37 [PATCH 00/29] constify scsi pci_device_id Arvind Yadav
2017-07-30 8:37 ` [PATCH 01/29] scsi: qla1280: constify pci_device_id Arvind Yadav
2017-07-30 8:37 ` [PATCH 02/29] scsi: qedi: " Arvind Yadav
2017-07-30 8:37 ` [PATCH 03/29] scsi: am53c974: " Arvind Yadav
2017-07-30 8:37 ` [PATCH 04/29] scsi: pm8001: " Arvind Yadav
2017-07-31 8:10 ` Jinpu Wang
2017-07-30 8:37 ` [PATCH 05/29] scsi: qla4xxx: " Arvind Yadav
2017-07-30 8:37 ` [PATCH 06/29] scsi: mvsas: " Arvind Yadav
2017-07-30 8:37 ` [PATCH 07/29] scsi: 3w-9xxx: " Arvind Yadav
2017-07-30 8:37 ` [PATCH 08/29] scsi: ipr: " Arvind Yadav
2017-07-30 8:37 ` [PATCH 09/29] scsi: arcmsr: " Arvind Yadav
2017-07-30 8:37 ` [PATCH 10/29] scsi: dpt_i2o: " Arvind Yadav
2017-07-31 7:56 ` [PATCH 00/29] constify scsi pci_device_id Johannes Thumshirn
2017-07-31 8:53 ` Arvind Yadav
2017-07-31 9:27 ` Johannes Thumshirn
2017-08-07 17:28 ` Martin K. Petersen [this message]
2017-08-08 6:34 ` Johannes Thumshirn
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=yq1tw1j9tjh.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=QLogic-Storage-Upstream@cavium.com \
--cc=aacraid@adaptec.com \
--cc=arvind.yadav.cs@gmail.com \
--cc=fthain@telegraphics.com.au \
--cc=gotom@debian.or.jp \
--cc=hare@suse.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=jinpu.wang@profitbricks.com \
--cc=jthumshirn@suse.de \
--cc=kashyap.desai@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=mdr@sgi.com \
--cc=mrochs@linux.vnet.ibm.com \
--cc=schmitzmic@gmail.com \
--cc=sumit.saxena@broadcom.com \
--cc=yokota@netlab.is.tsukuba.ac.jp \
/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