linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Ocean HY1 He <hehy1@lenovo.com>
Cc: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>,
	"tj@kernel.org" <tj@kernel.org>,
	"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Let AHCI dirver skip Lenovo SWRAID controller
Date: Tue, 26 Jan 2016 05:24:24 -0800	[thread overview]
Message-ID: <20160126132424.GA1993@infradead.org> (raw)
In-Reply-To: <56A76999.8050206@lenovo.com>

On Tue, Jan 26, 2016 at 12:42:43PM +0000, Ocean HY1 He wrote:
> Hi Alan,
> 
> Thanks for your comments!
> 
> Lenovo SWRAID driver is a closed source driver at this time, I am afraid 
> it's not possible to submit it to kernel.

So you're violating our copyright and want help for that?  Be ashamed!

> This patch is very important and critical for Lenovo next generation 
> Servers. I have tried to make sure this patch only impacts Lenovo 
> dedicated hardware and add a on/off boot option to end user who may 
> still wants using open source SWRAID(such as MDRAID).

The right ting is to always use mdraid and contribute the lenovo
superblock format to it, similar to how we support half a dozen other
non-native formats.

      reply	other threads:[~2016-01-26 13:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-25  3:11 [PATCH] Let AHCI dirver skip Lenovo SWRAID controller Ocean HY1 He
2016-01-25  9:56 ` Christoph Hellwig
2016-01-25 13:18 ` One Thousand Gnomes
2016-01-26 12:42   ` Ocean HY1 He
2016-01-26 13:24     ` Christoph Hellwig [this message]

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=20160126132424.GA1993@infradead.org \
    --to=hch@infradead.org \
    --cc=gnomes@lxorguk.ukuu.org.uk \
    --cc=hehy1@lenovo.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tj@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;
as well as URLs for NNTP newsgroup(s).