Re: [patch] pci: pci_enable_device_bars() fix

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Ingo Molnar
Date: Saturday, February 2, 2008 - 12:00 pm

* James Bottomley <James.Bottomley@HansenPartnership.com> wrote:


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
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[GIT PATCH] PCI patches for 2.6.24, Greg KH, (Fri Feb 1, 4:11 pm)
Re: [GIT PATCH] PCI patches for 2.6.24, Andrew Morton, (Fri Feb 1, 5:42 pm)
Re: [GIT PATCH] PCI patches for 2.6.24, Greg KH, (Fri Feb 1, 5:49 pm)
Re: [GIT PATCH] PCI patches for 2.6.24, Andrew Morton, (Fri Feb 1, 6:07 pm)
Re: [patch] pci: pci_enable_device_bars() fix, Jeff Garzik, (Sat Feb 2, 8:51 am)
Re: [patch] pci: pci_enable_device_bars() fix, James Bottomley, (Sat Feb 2, 9:01 am)
Re: [patch] pci: pci_enable_device_bars() fix, Ingo Molnar, (Sat Feb 2, 10:08 am)
Re: [patch] pci: pci_enable_device_bars() fix, Jeff Garzik, (Sat Feb 2, 10:33 am)
Re: [patch] pci: pci_enable_device_bars() fix, Ingo Molnar, (Sat Feb 2, 10:57 am)
Re: [patch] pci: pci_enable_device_bars() fix, James Bottomley, (Sat Feb 2, 11:08 am)
Re: [patch] pci: pci_enable_device_bars() fix, Jeff Garzik, (Sat Feb 2, 11:49 am)
Re: [patch] pci: pci_enable_device_bars() fix, Ingo Molnar, (Sat Feb 2, 12:00 pm)
Re: [patch] pci: pci_enable_device_bars() fix, Ingo Molnar, (Sat Feb 2, 12:35 pm)
Re: [patch] pci: pci_enable_device_bars() fix, Jeff Garzik, (Sat Feb 2, 1:48 pm)
Re: [patch] pci: pci_enable_device_bars() fix, Jeff Garzik, (Sat Feb 2, 1:56 pm)
Re: [patch] pci: pci_enable_device_bars() fix, Greg KH, (Sat Feb 2, 4:23 pm)
Re: [patch] pci: pci_enable_device_bars() fix, Ingo Molnar, (Mon Feb 4, 5:57 am)
Re: [patch] pci: pci_enable_device_bars() fix, Andrew Morton, (Mon Feb 4, 6:12 am)
Re: [patch] pci: pci_enable_device_bars() fix, Jeff Garzik, (Mon Feb 4, 8:30 am)
Re: [patch] pci: pci_enable_device_bars() fix, Jeff Garzik, (Mon Feb 4, 8:32 am)