From: Kevin Friedberg <kev.friedberg@gmail.com>
To: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: [PATCH] treat AHCI controllers under VMD as part of VMD
Date: Sun, 5 Feb 2023 01:23:04 -0500 [thread overview]
Message-ID: <CAEJbB42309TzwmbpJKrgjX-7Q8JRUN+1W4i3NDUsxfrn6L=_Jg@mail.gmail.com> (raw)
In-Reply-To: <20230201095421.000033f0@linux.intel.com>
Thank you! Three weeks in it's stable for me (and I do have a backup
just in case). But that's just on my system and having this properly
tested, validated and hopefully merged would be much better. This is
actually my first time working in C at this level, so any feedback is
appreciated.
Cheers,
Kevin
On Wed, Feb 1, 2023 at 3:54 AM Mariusz Tkaczyk
<mariusz.tkaczyk@linux.intel.com> wrote:
>
> Hi Kevin,
> Thank you for the patch. Please be aware that the RST is not officially
> supported on Linux. You are going to enable RST suppport using VROC Linux
> stack. You are using it at your own risk.
> Intel will review your patch and will run regression, it could take around
> month (sorry, we are getting back our labs now).
>
> Thanks,
> Mariusz
>
> On Wed, 25 Jan 2023 21:16:59 -0500
> Kevin Friedberg <kev.friedberg@gmail.com> wrote:
>
> > Detect when a SATA controller has been mapped under Intel Alderlake RST
> > VMD and list it as part of the domain, instead of independently, so that
> > it can use the VMD controller's RAID capabilities.
> >
> > Signed-off-by: Kevin Friedberg <kev.friedberg@gmail.com>
next prev parent reply other threads:[~2023-02-05 6:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-26 2:16 [PATCH] treat AHCI controllers under VMD as part of VMD Kevin Friedberg
2023-02-01 8:54 ` Mariusz Tkaczyk
2023-02-05 6:23 ` Kevin Friedberg [this message]
2023-02-07 8:44 ` Mariusz Tkaczyk
2023-02-09 0:39 ` Xiao Ni
2023-02-10 10:17 ` Mariusz Tkaczyk
2023-02-13 7:02 ` Kevin Friedberg
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='CAEJbB42309TzwmbpJKrgjX-7Q8JRUN+1W4i3NDUsxfrn6L=_Jg@mail.gmail.com' \
--to=kev.friedberg@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=mariusz.tkaczyk@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.