public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Grant Grundler <grundler@google.com>
Cc: David Miller <davem@davemloft.net>,
	akpm@linux-foundation.org, torvalds@linux-foundation.org,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PATCH] firs round of SCSI bug fixes for 2.6.29-rc1
Date: Fri, 16 Jan 2009 15:15:00 -0500	[thread overview]
Message-ID: <1232136901.3224.48.camel@localhost.localdomain> (raw)
In-Reply-To: <da824cf30901161209k7fa2d1cau27a2152c74256c4e@mail.gmail.com>

On Fri, 2009-01-16 at 12:09 -0800, Grant Grundler wrote:
> On Fri, Jan 16, 2009 at 11:10 AM, David Miller <davem@davemloft.net> wrote:
> ...
> >>
> >> TBH, I still wouldn't implement it the way LSI maintainers did.
> >> I'm happy they are the maintainers and it's their call.
> >
> > They are doing things which effect the entire system, not just
> > their driver.  So this doesn't fall under "maintainer's rights"
> 
> Agreed. This case is about a debug option which is normally disabled.
> So most people will never see this.
> 
> The thread was more about how to make the failure visible in a
> sane way WITHOUT the debug flag enabled. Then when the
> debug flag is enabled, panic the machine as well.
> 
> > If they fail locally, that's fine and perfectly expected, but to take
> > the whole machine out is another matter altogether.
> 
> Agreed.

Me too, but I rejected half of the LSI update because of other problems.
Since this is isolated to actual firmware debugging, which no normal
user will see, I let it go after a bit of arguing.

James



  reply	other threads:[~2009-01-16 20:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-16 14:56 [GIT PATCH] firs round of SCSI bug fixes for 2.6.29-rc1 James Bottomley
2009-01-16 17:09 ` Andrew Morton
2009-01-16 18:48   ` James Bottomley
2009-01-16 19:07     ` Andrew Morton
2009-01-16 20:28       ` James Bottomley
2009-01-16 19:09     ` David Miller
2009-01-16 19:02   ` Grant Grundler
2009-01-16 19:10     ` David Miller
2009-01-16 20:09       ` Grant Grundler
2009-01-16 20:15         ` James Bottomley [this message]
2009-01-17 21:17 ` Matthew Wilcox
2009-02-11  4:08   ` Matthew Wilcox
2009-02-11 12:42     ` 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=1232136901.3224.48.camel@localhost.localdomain \
    --to=james.bottomley@hansenpartnership.com \
    --cc=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=grundler@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --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