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
, Atul;
>Bagalkote, Sreenivas
>Subject: v2.4 megaraid2 update Re: [PATCH] Prevent NMI oopser
>
>
>Hi,
>
>As the megaraid2 maintainers dont seem to care about v2.4
>mainline at all, completly
>ignoring my requests to fix the NMI oopser bug for several
>months, I'm apply
Subject: v2.4 megaraid2 update Re: [PATCH] Prevent NMI oopser
Hi,
As the megaraid2 maintainers dont seem to care about v2.4
mainline at all, completly
ignoring my requests to fix the NMI oopser bug for several
months, I'm applying the RHEL3
update + inline reordering, which should do
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
Hi,
As the megaraid2 maintainers dont seem to care about v2.4 mainline at all,
completly
ignoring my requests to fix the NMI oopser bug for several months, I'm applying
the RHEL3
update + inline reordering, which should do it.
At this point I'm quite sure they wont answer this message
Hi,
As the megaraid2 maintainers dont seem to care about v2.4 mainline at all,
completly
ignoring my requests to fix the NMI oopser bug for several months, I'm applying
the RHEL3
update + inline reordering, which should do it.
At this point I'm quite sure they wont answer this message
6 matches
Mail list logo