From: Hans de Goede <hdegoede@redhat.com>
To: srinivas pandruvada <srinivas.pandruvada@linux.intel.com>,
markgross@kernel.org, ilpo.jarvinen@linux.intel.com,
andriy.shevchenko@linux.intel.com
Cc: platform-driver-x86@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/5] TPMI update for permissions
Date: Mon, 4 Dec 2023 15:06:26 +0100 [thread overview]
Message-ID: <f981896a-1c90-4475-84e8-7d459ffb97ed@redhat.com> (raw)
In-Reply-To: <e84824057954fa8593783c4433f5b535f0da6490.camel@linux.intel.com>
Hi Srinivas,
On 12/1/23 00:24, srinivas pandruvada wrote:
> On Thu, 2023-11-30 at 13:47 -0800, Srinivas Pandruvada wrote:
>> Process read/write and enabled state for feature drivers. When a
>> feature
>> is disabled, don't create a device to load a feature driver. When a
>> read
>> is blocked then don't load feature drivers. When write is blocked
>> continue
>> to function in read only mode.
>>
>> v2:
>> Dropped patch platform/x86/intel/tpmi: Add additional TPMI
>> header fields
>> Addressed other review comments, details are in each patch
>>
> lkp@intel.com is complaining that these patches can't be applied. I
> will fix any issue after review and post v3 if required.
Thanks.
I guess this may conflict with or depend on:
"[PATCH V6 00/20] intel_pmc: Add telemetry API to read counters"
which I have just merged into pdx86/review-hans, please make
sure your next version on top of pdx86/review-hans.
Regards,
Hans
>
> Thanks,
> Srinivas
>
>
>> Srinivas Pandruvada (5):
>> platform/x86/intel/tpmi: Don't create devices for disabled features
>> platform/x86/intel/tpmi: Modify external interface to get
>> read/write
>> state
>> platform/x86/intel/tpmi: Move TPMI ID definition
>> platform/x86: ISST: Process read/write blocked feature status
>> platform/x86/intel-uncore-freq: Process read/write blocked feature
>> status
>>
>> .../intel/speed_select_if/isst_tpmi_core.c | 25 +++++++++++++
>> drivers/platform/x86/intel/tpmi.c | 35 +++++++++--------
>> --
>> .../uncore-frequency/uncore-frequency-tpmi.c | 15 ++++++++
>> include/linux/intel_tpmi.h | 18 ++++++++--
>> 4 files changed, 72 insertions(+), 21 deletions(-)
>>
>
prev parent reply other threads:[~2023-12-04 14:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 21:47 [PATCH v2 0/5] TPMI update for permissions Srinivas Pandruvada
2023-11-30 21:47 ` [PATCH v2 1/5] platform/x86/intel/tpmi: Don't create devices for disabled features Srinivas Pandruvada
2023-12-04 14:03 ` Hans de Goede
2023-12-04 14:14 ` Ilpo Järvinen
2023-11-30 21:47 ` [PATCH v2 2/5] platform/x86/intel/tpmi: Modify external interface to get read/write state Srinivas Pandruvada
2023-11-30 21:47 ` [PATCH v2 3/5] platform/x86/intel/tpmi: Move TPMI ID definition Srinivas Pandruvada
2023-11-30 21:47 ` [PATCH v2 4/5] platform/x86: ISST: Process read/write blocked feature status Srinivas Pandruvada
2023-12-04 14:06 ` Hans de Goede
2023-12-04 14:11 ` Ilpo Järvinen
2023-12-04 14:19 ` Hans de Goede
2023-11-30 21:47 ` [PATCH v2 5/5] platform/x86/intel-uncore-freq: " Srinivas Pandruvada
2023-11-30 23:24 ` [PATCH v2 0/5] TPMI update for permissions srinivas pandruvada
2023-12-04 14:06 ` Hans de Goede [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=f981896a-1c90-4475-84e8-7d459ffb97ed@redhat.com \
--to=hdegoede@redhat.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markgross@kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=srinivas.pandruvada@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox