From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Ben Collins <bcollins@debian.org>
Cc: Marcel Lanz <marcel.lanz@ds9.ch>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PANIC] ohci1394 & copy large files
Date: Mon, 05 Apr 2004 10:07:56 +1000 [thread overview]
Message-ID: <1081123676.1203.128.camel@gaston> (raw)
In-Reply-To: <20040404231746.GX13168@phunnypharm.org>
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),
Ben.
next prev parent reply other threads:[~2004-04-05 0:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-04 14:16 [PANIC] ohci1394 & copy large files 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 [this message]
2004-04-05 0:12 ` Ben Collins
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=1081123676.1203.128.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=bcollins@debian.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 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.