From: Christoph Hellwig <hch@infradead.org>
To: "Mukker, Atul" <Atulm@lsil.com>
Cc: 'James Bottomley' <James.Bottomley@SteelEye.com>,
'Arjan van de Ven' <arjanv@redhat.com>,
'Paul Wagland' <paul@wagland.net>,
Matthew Wilcox <willy@debian.org>,
"Bagalkote, Sreenivas" <sreenib@lsil.com>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
"'linux-scsi@vger.kernel.org'" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH][BUGFIX] : megaraid patch for 2.10.1 (irq disable bug fix)
Date: Tue, 24 Feb 2004 20:43:27 +0000 [thread overview]
Message-ID: <20040224204327.A27822@infradead.org> (raw)
In-Reply-To: <0E3FA95632D6D047BA649F95DAB60E57033BC3DA@exa-atlanta.se.lsil.com>; from Atulm@lsil.com on Tue, Feb 24, 2004 at 11:04:21AM -0500
On Tue, Feb 24, 2004 at 11:04:21AM -0500, Mukker, Atul wrote:
> The driver package is available in usual location, too big to be inlined :-)
> ftp://ftp.lsil.com/pub/linux-megaraid/drivers/version-unified-2.20.0.0.02.24
> .2004-alpha1/
James already mentioned the probing issue and looking further through the
driver there's lots of need for improvement. I think we should try to get
2.6 merged up with all the changes from the last unified driver and additional
fixes posted to the list (e.g. the dma_sync thing, did you have a chance to
look at it?) so that we have a proben base until we look into it.
P.S. from a sort look the fusion-based adapters seem to be completely
different from existing megaraid adapters. What non-trivial code is
actually shared?
next prev parent reply other threads:[~2004-02-24 20:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-24 16:04 [PATCH][BUGFIX] : megaraid patch for 2.10.1 (irq disable bug fix) Mukker, Atul
2004-02-24 16:47 ` James Bottomley
2004-02-24 20:43 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-24 21:02 Mukker, Atul
2004-02-24 21:14 ` Arjan van de Ven
2004-02-24 14:47 Mukker, Atul
2004-02-24 14:58 ` Matthew Wilcox
2004-02-24 15:06 ` James Bottomley
2004-02-24 20:33 ` Matt Domsch
2004-02-23 17:24 Bagalkote, Sreenivas
2004-02-23 17:29 ` Matthew Wilcox
2004-02-24 7:09 ` Paul Wagland
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=20040224204327.A27822@infradead.org \
--to=hch@infradead.org \
--cc=Atulm@lsil.com \
--cc=James.Bottomley@SteelEye.com \
--cc=arjanv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=paul@wagland.net \
--cc=sreenib@lsil.com \
--cc=willy@debian.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