From: Ben Collins <bcollins@debian.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Marcel Lanz <marcel.lanz@ds9.ch>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PANIC] ohci1394 & copy large files
Date: Sun, 4 Apr 2004 20:12:13 -0400 [thread overview]
Message-ID: <20040405001213.GZ13168@phunnypharm.org> (raw)
In-Reply-To: <1081123676.1203.128.camel@gaston>
On Mon, Apr 05, 2004 at 10:07:56AM +1000, Benjamin Herrenschmidt wrote:
> On Mon, 2004-04-05 at 09:17, Ben Collins wrote:
>
> > Because the fix was pretty extensive and needed testing. It was
> > potentially more broken that the problem it was fixing. Sending untested
> > patches to Linus is far worse than batching a few up and pushing to him.
>
> Ok, makes sense, it wasn't just a 1-liner quick fix then ;)
>
> Still, from my experience, _very few_ people actually test things in
> trees like ieee1394, fbdev, etc... Even my tree isn't what it used
> to be for pmacs now that I'm fully in sync upstream.
>
> Even -mm lately haven't been as tested as it used to be (possibly
> because of upstream getting better). I find it's quite ok to send
> a fix that needs a bit more testing to a Linus -rc1 (but not later),
People that experience problems that I have a fix for in the repo,
usually get pointed to that repo for testing.
In this case I did the fix after -rc2, wasn't comfortable enough to send
it for -rc3 and I think I may wait for 2.6.6-rc1 since there's a harder
to reproduce bug now that I have to fix (I haven't seen it, but a few
people that tested our repo have reported it).
--
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
WatchGuard - http://www.watchguard.com/
next prev parent reply other threads:[~2004-04-05 0:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-04 14:16 Marcel Lanz
2004-04-04 14:13 ` Ben Collins
2004-04-04 23:00 ` Benjamin Herrenschmidt
2004-04-04 23:17 ` Ben Collins
2004-04-04 23:28 ` Randy.Dunlap
2004-04-05 0:09 ` Ben Collins
2004-04-05 0:07 ` Benjamin Herrenschmidt
2004-04-05 0:12 ` Ben Collins [this message]
2004-04-05 5:03 ` Dmitry Torokhov
2004-04-05 13:44 ` Ben Collins
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=20040405001213.GZ13168@phunnypharm.org \
--to=bcollins@debian.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel.lanz@ds9.ch \
/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
all inboxes | Powered by JetHome®