From: Christoph Hellwig <hch@infradead.org>
To: "Mukker, Atul" <Atul.Mukker@lsi.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC]: new LSI MegaRAID driver implementation
Date: Mon, 15 Feb 2010 13:18:23 -0500 [thread overview]
Message-ID: <20100215181823.GA25776@infradead.org> (raw)
In-Reply-To: <6C678488C5CEE74F813A4D1948FD2DC7B7668C0E@cosmail02.lsi.com>
On Mon, Feb 15, 2010 at 10:09:23AM -0700, Mukker, Atul wrote:
> We are anticipating about 70-80% of the current driver code to be changed. These changes would not be functional in nature though. The current functionality would be re-aligned in supporting functions. A parallel stream of functions would be created to support new HBAs.
>
> We are not anticipating changes in ways the new driver would work with the current generation of the HBAs and therefore we do not foresee any impact on the current functionality for these HBAs.
>
> We would like to solicit community feedback if this approach is acceptable. Alternative would be to leave the current driver untouched and submit a new driver for next generation of HBAs.
>
> Your inputs would be highly appreciated.
Please just add a new megaraid_<foo> driver, similar to how megaraid_sas
is split from the legacy megaraid driver. If the shared code is easy
enough to factor it could be moved into a megaraid_common module, but
in doubt I would not even bother with that.
next prev parent reply other threads:[~2010-02-15 18:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-15 17:09 [RFC]: new LSI MegaRAID driver implementation Mukker, Atul
2010-02-15 18:18 ` Christoph Hellwig [this message]
2010-02-16 16:37 ` Mukker, Atul
2010-02-16 16:45 ` Matthew Wilcox
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=20100215181823.GA25776@infradead.org \
--to=hch@infradead.org \
--cc=Atul.Mukker@lsi.com \
--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