From: Greg KH <greg@kroah.com>
To: Cheng Renquan <crquan@gmail.com>
Cc: Eric Moore <Eric.Moore@lsi.com>,
support@lsi.com, DL-MPTFusionLinux@lsi.com,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
chengrq@uit.com.cn
Subject: Re: [PATCH 2/2] mpt fusion: port "4.00.43.00" to mainstream git kernel
Date: Sun, 7 Dec 2008 20:59:15 -0800 [thread overview]
Message-ID: <20081208045915.GA14968@kroah.com> (raw)
In-Reply-To: <91b13c310812071851s5a82d52em63f86f1d3aa42ee9@mail.gmail.com>
On Mon, Dec 08, 2008 at 10:51:48AM +0800, Cheng Renquan wrote:
> Hi, all,
>
> I have tested and verified that these two patches can let my LSI-SAS-1068E
> controllers work well with 2.6.26.2 kernels, perfect,
>
> Tested-by: Cheng Renquan <crquan@gmail.com>
>
> but the latest git kernel has not yet been tested. just buildable. I
> personally suggest these patches integrated into Greg KH's staging
> tree. It seems meet staging's purpose well?
The staging tree is for new drivers that are not already included in the
kernel tree. Not for patches to existing drivers, that wouldn't really
work out.
thanks,
greg k-h
next prev parent reply other threads:[~2008-12-08 5:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-05 13:26 [PATCH 1/2] mpt fusion: updated mpt drivers from lsi upstream "4.00.43.00" crquan
2008-12-05 13:26 ` [PATCH 2/2] mpt fusion: port "4.00.43.00" to mainstream git kernel crquan
2008-12-08 2:51 ` Cheng Renquan
2008-12-08 4:59 ` Greg KH [this message]
2008-12-08 15:17 ` James Bottomley
[not found] ` <20081208140742.1c3a026d.akpm@linux-foundation.org>
2008-12-09 3:35 ` [PATCH 1/2] mpt fusion: updated mpt drivers from lsi upstream "4.00.43.00" Cheng Renquan
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=20081208045915.GA14968@kroah.com \
--to=greg@kroah.com \
--cc=DL-MPTFusionLinux@lsi.com \
--cc=Eric.Moore@lsi.com \
--cc=chengrq@uit.com.cn \
--cc=crquan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=support@lsi.com \
/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