public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: akpm@linux-foundation.org
Cc: linux-scsi@vger.kernel.org, hare@suse.de, Bo.Yang@lsi.com,
	Sumant.Patro@lsi.com
Subject: Re: [patch 02/17] Dell CERC support for megaraid_mbox
Date: Sun, 30 Mar 2008 12:13:40 -0500	[thread overview]
Message-ID: <1206897220.4224.50.camel@localhost.localdomain> (raw)
In-Reply-To: <200803282148.m2SLmXhQ012219@imap1.linux-foundation.org>

On Fri, 2008-03-28 at 14:48 -0700, akpm@linux-foundation.org wrote:
> From: Hannes Reinecke <hare@suse.de>
> 
> Newer Dell CERC firmware (>= 6.62) implement a random deletion handling
> compatible with the legacy megaraid driver.  The legacy handling shifted
> the target ID by 0x80 only for I/O commands (READ/WRITE/etc), whereas
> megaraid_mbox shifts the target ID always if random deletion is supported. 
> The resulted in megaraid_mbox sending an INQUIRY to the wrong channel, and
> not finding any devices, obviously.
> 
> So we disable the random deletion support if the offending firmware is
> found.
> 
> Addresses http://bugzilla.kernel.org/show_bug.cgi?id=6695

Bo,

You said you'd review this patch and give feedback "soon" twenty five
days ago (5 March).  My patience finally ran out on this one; you have
three days (that's until midnight CST on 2 April) to provide an ack or a
replacement patch for this otherwise I'll apply it anyway.

James



  reply	other threads:[~2008-03-30 17:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-28 21:48 [patch 02/17] Dell CERC support for megaraid_mbox akpm
2008-03-30 17:13 ` James Bottomley [this message]
2008-03-31 14:33   ` Yang, Bo
2008-04-02 21:48 ` Yang, Bo
2008-04-07 12:44   ` Hannes Reinecke
2008-04-14 15:56     ` Yang, Bo

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=1206897220.4224.50.camel@localhost.localdomain \
    --to=james.bottomley@hansenpartnership.com \
    --cc=Bo.Yang@lsi.com \
    --cc=Sumant.Patro@lsi.com \
    --cc=akpm@linux-foundation.org \
    --cc=hare@suse.de \
    --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