From: Ingo Molnar <mingo@elte.hu>
To: Jeff Garzik <jeff@garzik.org>
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, 2 Feb 2008 20:35:24 +0100 [thread overview]
Message-ID: <20080202193524.GC27927@elte.hu> (raw)
In-Reply-To: <47A4BB3C.6050709@garzik.org>
* Jeff Garzik <jeff@garzik.org> wrote:
>> so i'm still totally befuddled why you think that there was anything
>> particularly wrong or unhelpful about me replying to the specific
>> pull request that introduced a particular breakage into the kernel.
>> Had i mailed to lkml with a terse "kernel build broke" message with
>> just an URL to a config and the build breakage, you could rightfully
>> have complained that i should have done more to properly direct my
>> bugreport. But this breakage was about a PCI API change, the pull
>> request had a PCI mailing list Cc:-ed, why should i have thought that
>> this needs the attention of any other parties?
>
> Because the change required knowledge not only of PCI, but of the
> hardware in question. As your patch demonstrated.
>
> And yes -- the original changes should have been CC'd to interested
> parties as well. I'm still waiting to hear back from Alan or Bart
> whether the ATA/IDE changes in that PCI pile actually work... the
> original changeset even noted that relevant parties had not yet been
> queried.
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?
Ingo
next prev parent reply other threads:[~2008-02-02 19:35 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 [this message]
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
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=20080202193524.GC27927@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 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.