From: Hans de Goede <hdegoede@redhat.com>
To: "David E. Box" <david.e.box@linux.intel.com>,
gregkh@linuxfoundation.org, andriy.shevchenko@linux.intel.com,
srinivas.pandruvada@intel.com, mgross@linux.intel.com
Cc: linux-kernel@vger.kernel.org, platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH V6 0/3] Intel Software Defined Silicon
Date: Wed, 9 Feb 2022 13:23:09 +0100 [thread overview]
Message-ID: <4732c476-f380-196f-6f37-a5c3c749dd4e@redhat.com> (raw)
In-Reply-To: <20220208005444.487209-1-david.e.box@linux.intel.com>
Hi David,
On 2/8/22 01:54, David E. Box wrote:
> This series adds support for Intel Software Defined Silicon. These
> patches are the same as patches 4-6 from this series [1]. Patches 1-3
> of that series were pulled in during the 5.17 merge window.
>
> [1] https://lore.kernel.org/lkml/20211216023146.2361174-1-david.e.box@linux.intel.com/T/
Thank you for taking all the feedback from others into account
and doing new versions.
I was planning on doing an in-depth / foll review of this
today, but unfortunately a kernel regression somewhere else
has popped up and that is going to soak up all me work/$dayjob
time this week, sorry.
Assuming no major issues are found, the plan definitely is
to get this in before the 5.18 merge window. I've made a note
in my calendar to get a full review done no later then
February 17th.
Regards,
Hans
>
> David E. Box (3):
> platform/x86: Add Intel Software Defined Silicon driver
> tools arch x86: Add Intel SDSi provisiong tool
> selftests: sdsi: test sysfs setup
>
> .../ABI/testing/sysfs-driver-intel_sdsi | 77 +++
> MAINTAINERS | 7 +
> drivers/platform/x86/intel/Kconfig | 12 +
> drivers/platform/x86/intel/Makefile | 2 +
> drivers/platform/x86/intel/sdsi.c | 574 ++++++++++++++++++
> drivers/platform/x86/intel/vsec.c | 12 +-
> tools/arch/x86/intel_sdsi/Makefile | 9 +
> tools/arch/x86/intel_sdsi/sdsi.c | 540 ++++++++++++++++
> tools/testing/selftests/drivers/sdsi/sdsi.sh | 18 +
> .../selftests/drivers/sdsi/sdsi_test.py | 226 +++++++
> 10 files changed, 1476 insertions(+), 1 deletion(-)
> create mode 100644 Documentation/ABI/testing/sysfs-driver-intel_sdsi
> create mode 100644 drivers/platform/x86/intel/sdsi.c
> create mode 100644 tools/arch/x86/intel_sdsi/Makefile
> create mode 100644 tools/arch/x86/intel_sdsi/sdsi.c
> create mode 100755 tools/testing/selftests/drivers/sdsi/sdsi.sh
> create mode 100644 tools/testing/selftests/drivers/sdsi/sdsi_test.py
>
next prev parent reply other threads:[~2022-02-09 12:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 0:54 [PATCH V6 0/3] Intel Software Defined Silicon David E. Box
2022-02-08 0:54 ` [PATCH V6 1/3] platform/x86: Add Intel Software Defined Silicon driver David E. Box
2022-02-08 1:40 ` Joe Perches
2022-02-08 2:54 ` David E. Box
2022-02-08 5:34 ` Joe Perches
2022-02-08 5:55 ` David E. Box
2022-02-08 0:54 ` [PATCH V6 2/3] tools arch x86: Add Intel SDSi provisiong tool David E. Box
2022-02-08 0:54 ` [PATCH V6 3/3] selftests: sdsi: test sysfs setup David E. Box
2022-02-09 12:23 ` Hans de Goede [this message]
2022-02-09 16:46 ` [PATCH V6 0/3] Intel Software Defined Silicon David E. Box
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=4732c476-f380-196f-6f37-a5c3c749dd4e@redhat.com \
--to=hdegoede@redhat.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=david.e.box@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgross@linux.intel.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=srinivas.pandruvada@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 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).