public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH] aic94xx: fix SSP IU status print-out
Date: Tue, 02 Oct 2007 10:48:46 -0400	[thread overview]
Message-ID: <47025A4E.6040200@garzik.org> (raw)
In-Reply-To: <1191336373.3530.62.camel@localhost.localdomain>

James Bottomley wrote:
> On Tue, 2007-10-02 at 10:35 -0400, Jeff Garzik wrote:
>> James Bottomley wrote:
>>> On Tue, 2007-10-02 at 08:29 -0400, Jeff Garzik wrote:
>>>> James, what is the upstream status of my two aic94xx bug fixes?
>>>>
>>>> Have they been sent to Linus yet?
>>>>
>>>> Since you seem M.I.A., I'll send them upstream if I do not hear from you 
>>>> today.
>>> They're hardly -rc8 critical bug fixes, since no-one has noticed their
>>> effects for about 5 kernel releases.  I'll stick them into scsi-misc
>>> with the rest of the pending stuff.
>> Except for those people who want SMP to work, on platforms where 
>> TODEVICE actually matters.
> 
> And the number of bug reports on this?
> 
>> I'll send them upstream myself.
> 
> No, you won't; because that would be completely irresponsible.  You
> don't turn code for no reason at the last minute unless it's essential
> because of the danger of introducing inadvertent bugs along with the
> changes.  Since there are no users affected, there's zero benefit and
> there is a potential non-zero detriment to the code turn.
> 
> There's absolutely no reason to rush these into the release at the last
> minute.  The correct path is via scsi-misc and then to be backported
> into the stable series once we're sure they're OK.

What's irresponsible is holding onto simple, obvious bug fixes that 
obviously break certain scenarios.

	Jeff




  reply	other threads:[~2007-10-02 14:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-30 14:03 [PATCH] aic94xx: fix SSP IU status print-out Jeff Garzik
2007-10-02 12:29 ` Jeff Garzik
2007-10-02 14:20   ` James Bottomley
2007-10-02 14:35     ` Jeff Garzik
2007-10-02 14:46       ` James Bottomley
2007-10-02 14:48         ` Jeff Garzik [this message]
2007-10-02 15:00           ` James Bottomley
2007-10-02 17:11             ` Jeff Garzik
2007-10-02 17:26               ` James Bottomley

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=47025A4E.6040200@garzik.org \
    --to=jeff@garzik.org \
    --cc=James.Bottomley@SteelEye.com \
    --cc=linux-scsi@vger.kernel.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