public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Vasquez <andrew.vasquez@qlogic.com>
To: Christoph Hellwig <hch@infradead.org>,
	David Miller <davem@davemloft.net>,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
	James.Bottomley@SteelEye.com, ema@debian.org
Subject: Re: Major qla2xxx regression on sparc64
Date: Wed, 18 Apr 2007 10:28:02 -0700	[thread overview]
Message-ID: <20070418172802.GD12708@andrew-vasquezs-computer.local> (raw)
In-Reply-To: <20070418171346.GA16471@infradead.org>

On Wed, 18 Apr 2007, Christoph Hellwig wrote:

> I don't think a module option is a good idea at this point.  The problem
> is you broke some so far perfectly working setups, which is not okay.
> The only first step can be printing a really big warning.  After this
> has been in for a while (at lest half a year) we can make it a non-default
> option or turn if off completely in case the warning never triggered in
> practice.
> 
> The only resonable thing for 2.6.21 is to put in David's patch, possible
> with an even more drastic warning when the rom is invalid and there's
> no prom-fallback available.
> 
> Note that I expect Sun put in the invalid ROM intentionally, as we have
> similar cases with other cards that have totally messed up ROMs in
> Sun-branded versions.  Personally I think that's an utterly bad decision
> from Sun's side, but we'll have to live with this.

Fine.  I'll rework an alternate patch for the 2.6.22 timeframe...


  reply	other threads:[~2007-04-18 17:28 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-16  8:02 Major qla2xxx regression on sparc64 David Miller
2007-04-16 16:37 ` Andrew Vasquez
2007-04-16 19:37   ` David Miller
2007-04-16 19:59     ` David Miller
2007-04-16 20:08     ` Andrew Vasquez
2007-04-16 21:10       ` Andrew Vasquez
2007-04-16 22:08         ` David Miller
2007-04-16 22:25           ` Andrew Vasquez
2007-04-16 22:29             ` David Miller
2007-04-16 23:28               ` Andrew Vasquez
2007-04-16 23:41                 ` David Miller
2007-04-16 23:47                   ` Andrew Vasquez
2007-04-17  0:05                     ` David Miller
2007-04-17  2:41                       ` Andrew Vasquez
2007-04-17  5:02                         ` David Miller
2007-04-17 18:28                           ` Seokmann Ju
2007-04-17 18:56                             ` David Miller
2007-04-18 17:16                             ` Christoph Hellwig
2007-04-18 20:12                               ` David Miller
2007-04-18 17:13       ` Christoph Hellwig
2007-04-18 17:28         ` Andrew Vasquez [this message]
2007-04-18 20:13           ` David Miller
2007-04-19 17:15             ` Andrew Vasquez
2007-04-18 20:10         ` David Miller
2007-04-22 14:31           ` Christoph Hellwig

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=20070418172802.GD12708@andrew-vasquezs-computer.local \
    --to=andrew.vasquez@qlogic.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=davem@davemloft.net \
    --cc=ema@debian.org \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --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