From: Jeff Garzik <jeff@garzik.org>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: 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: Thu, 24 May 2007 16:52:46 -0400 [thread overview]
Message-ID: <4655FB1E.7050701@garzik.org> (raw)
In-Reply-To: <1180015447.3692.6.camel@mulgrave.il.steeleye.com>
James Bottomley wrote:
> On Thu, 2007-05-24 at 01:51 -0400, Jeff Garzik wrote:
>> James Bottomley wrote:
>>> It's not a bug fix or even an enhancement. Historically, it is quite
>>> difficult to get maintainers to ack these ... particularly if you don't
>>> cc them.
>> If neither you nor the maintainers are reading and responding to patches
>> sent to linux-scsi, I don't think the problem is sitting in my chair.
>
> Oh come off it ... You've been around long enough to know that
> 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.
If individual driver maintainers are not paying attention to what is
going on in their subsystem, and in the kernel as a whole, then the
problem does not lie with the external patch author.
Jeff
next prev parent reply other threads:[~2007-05-24 20:52 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
2007-05-24 20:52 ` Jeff Garzik [this message]
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=4655FB1E.7050701@garzik.org \
--to=jeff@garzik.org \
--cc=James.Bottomley@SteelEye.com \
--cc=akpm@linux-foundation.org \
--cc=andrew.vasquez@qlogic.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mark_salyzyn@adaptec.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.