public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Greg KH <gregkh@suse.de>, Linus Torvalds <torvalds@osdl.org>,
	Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz,
	pcihpd-discuss@lists.sourceforge.net,
	linux-scsi <linux-scsi@vger.kernel.org>,
	James Bottomley <James.Bottomley@HansenPartnership.com>
Subject: Re: [patch] pci: pci_enable_device_bars() fix
Date: Sat, 02 Feb 2008 15:48:31 -0500	[thread overview]
Message-ID: <47A4D71F.3060009@garzik.org> (raw)
In-Reply-To: <20080202193524.GC27927@elte.hu>

Ingo Molnar wrote:
> so please tell me Jeff. If Greg, who is the super-maintainer of your 
> code area, and who deals with your code every day and changes it every 
> minute and hour, simply did not Cc: the SCSI list - how am i, a largely 
> outside party in this matter, supposed to notice that 3 maintainers and 
> 3 mailing lists in the Cc: were somehow not enough and that i was 
> supposed to grow the already sizable Cc: list even more?

Because, regardless of the situation, it's both common courtesy and wise 
practice to CC relevant driver maintainers, when you touch a driver.

And it's just common sense:  Greg simply does not know the intimate 
details of every PCI driver.  Nor do I.  Nor you.

In the case of lpfc here, we have an active driver maintainer, and an 
up-to-date MAINTAINERS entry.  Even if you are too slack to read 
MAINTAINERS, 'git log' would have given you the same info.

Don't pretend there is some benefit here to ignoring the people that 
best know the driver.  I don't buy that; it simply makes no engineering 
sense whatsoever.

	Jeff



  reply	other threads:[~2008-02-02 20:48 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-01 23:11 [GIT PATCH] PCI patches for 2.6.24 Greg KH
2008-02-02  0:42 ` Andrew Morton
2008-02-02  0:49   ` Greg KH
2008-02-02  1:07     ` Andrew Morton
2008-02-02 11:13 ` [patch] pci: pci_enable_device_bars() fix (was: [GIT PATCH] PCI patches for 2.6.24) Ingo Molnar
2008-02-02 15:51   ` [patch] pci: pci_enable_device_bars() fix Jeff Garzik
2008-02-02 16:01     ` James Bottomley
2008-02-02 17:08     ` Ingo Molnar
2008-02-02 17:33       ` Jeff Garzik
2008-02-02 17:57         ` Ingo Molnar
2008-02-02 18:49           ` Jeff Garzik
2008-02-02 19:35             ` Ingo Molnar
2008-02-02 20:48               ` Jeff Garzik [this message]
2008-02-04 12:57                 ` Ingo Molnar
2008-02-04 13:12                   ` Andrew Morton
2008-02-04 15:32                     ` Jeff Garzik
2008-02-04 15:30                   ` Jeff Garzik
2008-02-02 18:08       ` James Bottomley
2008-02-02 19:00         ` Ingo Molnar
2008-02-02 18:44   ` [patch] pci: pci_enable_device_bars() fix (was: [GIT PATCH] PCI patches for 2.6.24) Greg KH
2008-02-02 19:05     ` Ingo Molnar
2008-02-02 20:56       ` [patch] pci: pci_enable_device_bars() fix Jeff Garzik
2008-02-02 23:23         ` Greg KH

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=47A4D71F.3060009@garzik.org \
    --to=jeff@garzik.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=akpm@osdl.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=pcihpd-discuss@lists.sourceforge.net \
    --cc=torvalds@osdl.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