public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
	Jeff Garzik <jeff@garzik.org>,
	akpm@linux-foundation.org, linux-scsi@vger.kernel.org, "Salyzyn,
	Mark" <mark_salyzyn@adaptec.com>,
	Andrew Vasquez <andrew.vasquez@qlogic.com>
Subject: Re: [patch 14/25] SCSI: use irq_handler_t where appropriate
Date: Fri, 25 May 2007 11:06:19 +0200	[thread overview]
Message-ID: <4656A70B.60906@s5r6.in-berlin.de> (raw)
In-Reply-To: <20070524081720.5675ad5d.randy.dunlap@oracle.com>

Randy Dunlap wrote:
> On Thu, 24 May 2007 09:04:06 -0500 James Bottomley wrote:
>> maintainers are not always watching everything ... it would be nice if
>> they were, but to give a patch the best shot at review, you try to
>> attract their attention.  Specifically, in this case, you should cc the
>> maintainers and you should have a subject line explaining that you are
>> modifying their driver.  It is very easy to ignore a patch that's simply
>> waved at the SCSI list with a generic subject line.
> 
> I can understand subsystem maintainers ignoring lkml, but ignoring
> the subsystem mailing list makes no sense to me, especially if the
> subject contains "[PATCH]".

I mostly agree.  It becomes difficult with cross-subsystem patches
though.  The difficulty with such patches is that the subsystem
mailinglist which was chosen as adressee doesn't tell the whole picture,
and the subject, even if chosen carefully, often cannot explicitly tell
which places it touches.

On the other hand, submitters of nontrivial cross-subsystem patches can
be expected to put some extra care in their submission, i.e. to add
respective personal addresses.  (And of course to include a diffstat!)

The patch "SCSI: use irq_handler_t where appropriate" is of course not a
patch of this kind.  Also, it is of the sort which IMO doesn't need a
driver maintainer's ACK in the first place.  Sure, it wouldn't have hurt
a lot to call it for example "SCSI: use irq_handler_t in aacraid and
qla2xxx", even though that information will be redundant /after/ it went
into a git tree.
-- 
Stefan Richter
-=====-=-=== -=-= ==--=
http://arcgraph.de/sr/

  parent reply	other threads:[~2007-05-25  9:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-23 21:41 [patch 14/25] SCSI: use irq_handler_t where appropriate akpm
2007-05-23 22:07 ` Jeff Garzik
2007-05-23 22:16   ` Andrew Morton
2007-05-23 22:55   ` James Bottomley
2007-05-24  5:51     ` Jeff Garzik
2007-05-24 14:04       ` James Bottomley
2007-05-24 14:28         ` Salyzyn, Mark
2007-05-24 15:21           ` James Bottomley
2007-05-26 20:45             ` James Bottomley
2007-05-24 15:17         ` Randy Dunlap
2007-05-24 15:28           ` James Bottomley
2007-05-24 20:49             ` Jeff Garzik
2007-05-25  9:32               ` Stefan Richter
2007-05-25  9:06           ` Stefan Richter [this message]
2007-05-24 20:52         ` Jeff Garzik
2007-05-24 13:32     ` Salyzyn, Mark
2007-05-23 23:00   ` David Miller
2007-05-24 11:31 ` Andrew Vasquez

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=4656A70B.60906@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=James.Bottomley@SteelEye.com \
    --cc=akpm@linux-foundation.org \
    --cc=andrew.vasquez@qlogic.com \
    --cc=jeff@garzik.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mark_salyzyn@adaptec.com \
    --cc=randy.dunlap@oracle.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