From: Matthew Wilcox <willy@debian.org>
To: "Hammer, Jack" <Jack_Hammer@adaptec.com>
Cc: Adrian Bunk <bunk@fs.tum.de>,
Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: 2.4.28-pre3: broken ips update
Date: Mon, 13 Sep 2004 15:42:30 +0100 [thread overview]
Message-ID: <20040913144230.GU642@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <A121ABA5B472B74EB59076B8E3C8F019796579@rtpe2k01.adaptec.com>
On Mon, Sep 13, 2004 at 10:28:44AM -0400, Hammer, Jack wrote:
> This trivial one line patch corrects my mistake in ips.h. I assure you
> that the previous patch was compiled and tested extensively - over a
> several month test cycle. However, our testing concentrates on existing
> customers and shipping distro's. Most of those changed to the 2.6
> kernel on or before 2.4.20, so we had no 2.4 kernel in our test matrix
> beyond that. I apologize for the oversight - we must update our test
> matrix to always check out latest 2.4 development kernel.
>
> The concerns expressed below about this driver being "blindly submitted"
> or is "untested" are completely unwarranted.
I disagree. Your testing, while I'm sure is long drawn out and massively
complicated, is missing the crucial element of testing what you're
submitting against. I don't think you need to check the latest bleeding
unstable kernel in your test runs, partly because it changes so fast, and
partly because you'll start to hit bugs that are unrelated to your driver.
But you absolutely must at least test compiling your driver against the
tree you submit it against, and a quick boot of the resulting kernel
wouldn't add much time to your patch submission process.
--
"Next the statesmen will invent cheap lies, putting the blame upon
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince
himself that the war is just, and will thank God for the better sleep
he enjoys after this process of grotesque self-deception." -- Mark Twain
next prev parent reply other threads:[~2004-09-13 14:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-13 14:28 2.4.28-pre3: broken ips update Hammer, Jack
2004-09-13 14:42 ` Matthew Wilcox [this message]
2004-09-13 14:46 ` Arjan van de Ven
-- strict thread matches above, loose matches on Subject: below --
2004-09-13 18:01 Hammer, Jack
2004-09-13 15:00 Hammer, Jack
[not found] <20040911220117.GA4669@logos.cnet>
2004-09-13 7:03 ` Adrian Bunk
2004-09-13 14:24 ` Mikael Pettersson
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=20040913144230.GU642@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=Jack_Hammer@adaptec.com \
--cc=bunk@fs.tum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
/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