From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: "Bagalkote, Sreenivas" <sreenib@lsil.com>
Cc: "Andrey J. Melnikoff (TEMHOTA)" <temnota@kmv.ru>,
Vasily Averin <vvs@sw.ru>, Matt Domsch <Matt_Domsch@dell.com>,
linux-kernel@vger.kernel.org, "Mukker, Atul" <Atulm@lsil.com>
Subject: Re: v2.4 megaraid2 update Re: [PATCH] Prevent NMI oopser
Date: Wed, 2 Mar 2005 17:55:44 -0300 [thread overview]
Message-ID: <20050302205544.GB4100@logos.cnet> (raw)
In-Reply-To: <0E3FA95632D6D047BA649F95DAB60E570230CBEC@exa-atlanta>
On Wed, Mar 02, 2005 at 11:26:06AM -0500, Bagalkote, Sreenivas wrote:
> Hello Marcelo,
Hi Sreenivas,
Damn, now I apologize for taking so long to answer...
> As per our offline conversation, I have verified the update that went into
> 2.4.30-pre2.
> I confirm that all changes are correct. I have only one doubt: The driver
> was using
> sleep_on_timeout for lack of msleep. Should it start using msleep now?
I dont see the need for msleep() given that sleep_on_timeout() schedules.
The problematic EH code which used udelay() was removed AFAICS.
> Vasily & Andrey, thank you for your efforts.
I appreciate your offline message that you're compromised to
keep an eye on v2.4 megaraid2 from now on :)
next prev parent reply other threads:[~2005-03-03 1:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-02 16:26 v2.4 megaraid2 update Re: [PATCH] Prevent NMI oopser Bagalkote, Sreenivas
2005-03-02 20:55 ` Marcelo Tosatti [this message]
[not found] <41F5FC96.2010103@sw.ru>
2005-01-31 23:17 ` Marcelo Tosatti
2005-02-02 18:42 ` Vasily Averin
2005-02-02 19:06 ` Matt Domsch
2005-02-02 19:32 ` Vasily Averin
2005-02-02 20:19 ` Matt Domsch
[not found] ` <20050207202745.GA19104@kmv.ru>
2005-02-23 7:06 ` v2.4 megaraid2 update " Marcelo Tosatti
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=20050302205544.GB4100@logos.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=Atulm@lsil.com \
--cc=Matt_Domsch@dell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sreenib@lsil.com \
--cc=temnota@kmv.ru \
--cc=vvs@sw.ru \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.