From: Paul Mundt <lethal@linux-sh.org>
To: Jeff Garzik <jeff@garzik.org>
Cc: Magnus Damm <magnus.damm@gmail.com>,
linuxsh-dev@lists.sourceforge.net, linux-ide@vger.kernel.org,
Sonic Zhang <sonic.adi@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] pata_platform: Fix NULL pointer dereference
Date: Tue, 17 Jul 2007 20:01:30 +0900 [thread overview]
Message-ID: <20070717110130.GA25718@linux-sh.org> (raw)
In-Reply-To: <469C98F5.50101@garzik.org>
On Tue, Jul 17, 2007 at 06:24:53AM -0400, Jeff Garzik wrote:
> It's just reality that there are never enough people to verify every
> patch before it goes in. We just support way too much hardware for that
> to be remotely feasible. Sure we -try- to keep the driver maintainer
> CC'd, but alas we are human.
>
Try? I've never _once_ received a CC from you regarding a change to
pata_platform. The only time I've been CC'ed at all is when someone
submitting the patch had the common courtesy to do so.
Whereas the number of times I've had to clean up after something merged
behind my back has been higher than the number of times I've been CC'ed
on any of these changes.
> Your thinking is flawed if you think I'm going to hold up every patch
> until it's verified on each of 63 ATA controller drivers, when I make a
> core change, for example. Not scalable. We scale in another way:
>
This has nothing to do with core changes that impact every driver, this
has to do with isolated changes to a _single_ driver that you're
obviously not in a position to test. That's a very different situation.
Again, if you can't be bothered to CC people on changes to their drivers
that aren't libata-wide, don't apply them in the first place. I would
much rather play API catch up with my driver than have to backtrack and
figure out what went wrong when suddenly all of my boards stop booting.
Your "merge first and hope someone else notices and fixes it later"
approach is insane. We've never done kernel development like that, libata
isn't special.
next prev parent reply other threads:[~2007-07-17 11:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-17 8:42 [PATCH] pata_platform: Fix NULL pointer dereference Magnus Damm
2007-07-17 9:02 ` Paul Mundt
2007-07-17 9:33 ` Jeff Garzik
2007-07-17 9:47 ` Paul Mundt
2007-07-17 10:24 ` Jeff Garzik
2007-07-17 11:01 ` Paul Mundt [this message]
2007-07-18 9:32 ` Magnus Damm
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=20070717110130.GA25718@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=akpm@linux-foundation.org \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linuxsh-dev@lists.sourceforge.net \
--cc=magnus.damm@gmail.com \
--cc=sonic.adi@gmail.com \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).