public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: "Salyzyn, Mark" <mark_salyzyn@adaptec.com>
Cc: Judith Lebzelter <judith@linux-foundation.org>,
	vgoyal@in.ibm.com, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] aacraid: [Fastboot] Panics for AACRAID driverduring'insmod' for kexec test [take 4]
Date: Tue, 03 Apr 2007 11:09:54 -0500	[thread overview]
Message-ID: <1175616594.3645.26.camel@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <AE4F746F2AECFC4DA4AADD66A1DFEF017AA267@otce2k301.adaptec.com>

On Tue, 2007-04-03 at 11:58 -0400, Salyzyn, Mark wrote:
> I will do you one better, James, I will slip in a little cleanup in
> sa.c (support file for the old PPC based ARC cards) where I discovered
> the restart platform function was ALSO left unset which could result
> in similar pain of null pointer discovery.

Actually, for 2.6.21-rc5 could I just have the two strict bug fixes for
the potential oops you spotted ...  I should really be adding feature
changes or cleanups at this stage of the kernel release.

I can put all the rest into scsi-misc for post 2.6.21

Thanks,

James



  reply	other threads:[~2007-04-03 16:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1175611901.3645.3.camel@mulgrave.il.steeleye.com>
2007-04-03 15:58 ` [PATCH] aacraid: [Fastboot] Panics for AACRAID driverduring'insmod' for kexec test [take 4] Salyzyn, Mark
2007-04-03 16:09   ` James Bottomley [this message]
2007-04-03 16:14     ` [PATCH] aacraid: [Fastboot] Panics for AACRAIDdriverduring'insmod' for kexec test [take 5] Salyzyn, Mark
2007-04-04 19:49       ` [PATCH] aacraid: Correct SMC products in aacraid.txt Salyzyn, Mark
2007-04-03 16:54   ` [PATCH] aacraid: [Fastboot] Panics for AACRAID driverduring'insmod' for kexec test [take 4] Judith Lebzelter

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=1175616594.3645.26.camel@mulgrave.il.steeleye.com \
    --to=james.bottomley@steeleye.com \
    --cc=judith@linux-foundation.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mark_salyzyn@adaptec.com \
    --cc=vgoyal@in.ibm.com \
    /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