From: Andrew Morton <akpm@osdl.org>
To: "Ju, Seokmann" <Seokmann.Ju@lsil.com>
Cc: Seokmann.Ju@engenio.com, andre@linux-ide.org,
James.Bottomley@SteelEye.com, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH 1/1] megaraid_{mm,mbox}: fix a bug in reset handler
Date: Tue, 18 Apr 2006 13:37:22 -0700 [thread overview]
Message-ID: <20060418133722.7af041e3.akpm@osdl.org> (raw)
In-Reply-To: <890BF3111FB9484E9526987D912B261901BCDA@NAMAIL3.ad.lsil.com>
"Ju, Seokmann" <Seokmann.Ju@lsil.com> wrote:
>
> I've seen the patch (megaraid_mmmbox_fix_a_bug_in_reset_handler.patch) available on 2.6.17-rc1-mm3 under "SCSI warning fix" section.
> What should I do to remove "warning" tag on the patch.
> I've attached another patch in previous email that has 'udelay()' in the loop to remove NMI concern, and waiting for confirmation on it. Will this change remove the "warning"?
>
> I'll submit the patch officially by end of today.
There are four megaraid-specific patches in -mm:
megaraid-unused-variable.patch
drivers-scsi-megaraidc-add-a-dummy-mega_create_proc_entry-for-proc_fs=y.patch
scsi-megaraid-megaraid_mmc-fix-a-null-pointer-dereference.patch
megaraid_mmmbox-fix-a-bug-in-reset-handler.patch
The final one is your latest patch.
I'll periodically send such patches to the subsystem maintainer until
something happens.
next prev parent reply other threads:[~2006-04-18 20:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-18 14:50 Ju, Seokmann
2006-04-18 16:33 ` Andre Hedrick
2006-04-18 20:37 ` Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-04-18 17:28 Ju, Seokmann
2006-04-17 13:12 Ju, Seokmann
2006-04-12 13:09 Ju, Seokmann
2006-04-13 5:00 ` Andrew Morton
2006-04-13 5:05 ` Andrew Morton
2006-04-15 7:10 ` Andre Hedrick
2006-04-15 14:00 ` 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=20060418133722.7af041e3.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=James.Bottomley@SteelEye.com \
--cc=Seokmann.Ju@engenio.com \
--cc=Seokmann.Ju@lsil.com \
--cc=andre@linux-ide.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
all inboxes | Powered by JetHome®