From: Alan Cox <gnomes@lxorguk.ukuu.org.uk>
To: "David F." <df7729@gmail.com>
Cc: Dennis Mungai <dmngaie@gmail.com>,
Christoph Hellwig <hch@infradead.org>,
"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>,
linux-ide@vger.kernel.org,
Dan Williams <dan.j.williams@intel.com>,
linux-nvme@lists.infradead.org
Subject: Re: When will Linux support new RAID controllers
Date: Thu, 7 Dec 2017 14:16:12 +0000 [thread overview]
Message-ID: <20171207141612.2653a0fb@alans-desktop> (raw)
In-Reply-To: <CAGRSmLto7dG19zgUkdZjuhacWXo=ju6WdS0YVjC5xOOsGjV9kg@mail.gmail.com>
On Mon, 4 Dec 2017 18:01:10 -0800
"David F." <df7729@gmail.com> wrote:
> Hi,
>
> Any word if the patch is available?
>
> Is this going mainline anytime soon?
I am not aware of anyone in Intel working on it or planning to work on it
at this point. Nothing stops someone outside of Intel doing that from the
code that was released.
For things that need BIOS changes whatever the vendor my experience has
always been that you make the most impact by talking to the actual system
vendor (who controls the BIOS), including telling them why you didn't buy
their machine. At the end of the day businesses make decisions based on
dollars.
Alan
next prev parent reply other threads:[~2017-12-07 14:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAGRSmLs-Hr+FFfa4_29kidEeL2d7b+cEP6u1OkOUoYW6Cm15BA@mail.gmail.com>
2017-11-10 13:19 ` When will Linux support new RAID controllers Christoph Hellwig
2017-11-10 13:31 ` Dennis Mungai
2017-11-10 19:06 ` David F.
2017-12-05 2:01 ` David F.
2017-12-07 0:00 ` Christoph Hellwig
2017-12-07 14:16 ` Alan Cox [this message]
2017-12-07 14:18 ` Dennis Mungai
2017-12-13 20:20 ` David F.
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=20171207141612.2653a0fb@alans-desktop \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=dan.j.williams@intel.com \
--cc=df7729@gmail.com \
--cc=dmngaie@gmail.com \
--cc=hch@infradead.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-raid@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