From: Ingo Molnar <mingo@elte.hu>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Jeff Garzik <jeff@garzik.org>, 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>
Subject: Re: [patch] pci: pci_enable_device_bars() fix
Date: Sat, 2 Feb 2008 20:00:53 +0100 [thread overview]
Message-ID: <20080202190053.GA27927@elte.hu> (raw)
In-Reply-To: <1201975706.3187.36.camel@localhost.localdomain>
* James Bottomley <James.Bottomley@HansenPartnership.com> wrote:
> Are you seriously telling us that it required too much investigation
> on your part to figure out that something with a compile failure in
> drivers/scsi might belong on the scsi list?
This is getting silly. Let me repeat it, because IMO it's really
straightforward. My (quick) investigation based on the function name
that was in the error message:
drivers/scsi/lpfc/lpfc_init.c:1897: error: implicit declaration
of function 'pci_enable_device_bars'
a straightforward search on "pci_enable_device_bars" led to a recent PCI
API related change pushed by Greg, with the following straightforward
subject line:
[GIT PATCH] PCI patches for 2.6.24
http://lkml.org/lkml/2008/2/1/483
the email had this description:
| Some general cleanups, minor tweaks, and a bit of PCI hotplug
| updates, and some PCI Express updates for new features, if your
| hardware happens to support it.
furthermore, the mail already had two PCI mailing lists in its Cc: line.
The PCI subsystem regularly does cross-treee changes, by its nature.
i had all reasons to believe that this was a (innocious looking) PCI
subsystem change and a harmless (but a tad under-tested) API cleanup
that went haywire: it smelled like PCI, it walked like PCI and it
quacked like PCI.
So to me it was clearly a PCI merge not an SCSI merge, and i was really
only interested in the first hop, i.e. i was primarily interested in the
pull request that clearly changed multiple subsystems, and a seemingly
API change that broke the build.
Three mailing lists and three maintainers were already on the Cc: line
for that pull request. So tell me, exactly what should have let me to
believe that i should have added anyone else to the _already_ sizable
Cc: line?? I could have done it, had i have more time and had i realized
the full scope of the change and the somewhat misleading Cc:s that were
on the original pull request, but i clearly was not _required_ to - and
your suggestions to the contrary are ridiculous.
Furthermore i reject the sometimes derogatory undertone of your mails
that implies that i should somehow have done more or different work than
i already did.
I really hope you treat other contributors and bug-reporters better than
you treated me :( Shall this be my last voluntary SCSI contribution for
a good while.
Ingo
next prev parent reply other threads:[~2008-02-02 19:01 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
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 [this message]
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=20080202190053.GA27927@elte.hu \
--to=mingo@elte.hu \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@osdl.org \
--cc=gregkh@suse.de \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=linux-scsi@vger.kernel.org \
--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