public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "Yang, Bo" <Bo.Yang@lsi.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"akpm@osdl.org" <akpm@osdl.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Austria, Winston" <Winston.Austria@lsi.com>,
	"Mukker, Atul" <Atul.Mukker@lsi.com>
Subject: Re: [PATCH 9/12] scsi: megaraid_sas - Fix the fix for fw hang caused by megaraid sas application
Date: Tue, 13 Oct 2009 17:26:57 +0000	[thread overview]
Message-ID: <1255454817.2855.211.camel@localhost.localdomain> (raw)
In-Reply-To: <4B6A08C587958942AA3002690DD4F8C35C6861E8@cosmail02.lsi.com>

On Tue, 2009-10-06 at 14:47 -0600, Yang, Bo wrote:
> RESUBMIT:
> 
> Added the fix for FW and OS hang by using MSM.  Also add the fix for pending cmd in fw, after deleting the lds.

This is practically unintelligible as a changelog.  These logs get used
by distibutions and other people trying to determine if they need the
patch based on bug reports they're seeing

>From the patch I think what you've done is:

1. Added a lock to the skinny firmware initialisation sequence to
prevent the two stage write being non atomic if multiple instances use
it.
2. Added a flag to the driver shutdown sequence to prevent aen ioctls
being called after shutdown begins.

For the future, could we also have separate bug fixes in separate
patches, please.

Also, does this need to go to stable?

Thanks,

James

      reply	other threads:[~2009-10-13 17:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4B6A08C587958942AA3002690DD4F8C35C5119BC@cosmail02.lsi.com>
2009-09-21  2:44 ` [PATCH 9/12] scsi: megaraid_sas - Fix the fix for fw hang caused by megaraid sas application Yang, Bo
2009-10-06 20:47   ` Yang, Bo
2009-10-13 17:26     ` James Bottomley [this message]

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=1255454817.2855.211.camel@localhost.localdomain \
    --to=james.bottomley@hansenpartnership.com \
    --cc=Atul.Mukker@lsi.com \
    --cc=Bo.Yang@lsi.com \
    --cc=Winston.Austria@lsi.com \
    --cc=akpm@osdl.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