From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: hansg@kernel.org,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Cc: platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, sammiee5311@gmail.com
Subject: Re: [PATCH 0/2] platform/x86: ISST: SST-PP failure handling
Date: Tue, 18 Aug 2026 17:07:47 +0300 [thread overview]
Message-ID: <178706206786.20251.8243742243633437618.b4-ty@b4> (raw)
In-Reply-To: <20260811222134.3912626-1-srinivas.pandruvada@linux.intel.com>
On Tue, 11 Aug 2026 15:21:32 -0700, Srinivas Pandruvada wrote:
> Some optimizations to fail on SST-PP and add sst_instance check
> for a package.
>
> This series is dependent on series "platform/x86: ISST: Validate
> inputs."
>
> Srinivas Pandruvada (2):
> platform/x86: ISST: Return error during profile addition
> platform/x86: ISST: Add a NULL check for sst_inst[]
>
> [...]
Thank you for your contribution, it has been applied to my local
review-ilpo-next branch. Note it will show up in the public
platform-drivers-x86/review-ilpo-next branch only once I've pushed my
local branch there, which might take a while.
FYI [if applicable to your patch], as per Linus' policy change, also
fixes are mostly routed through for-next unless the fix is for a
commit introduced in the most recent cycle or is clearly a regression
fix.
The list of commits applied:
[1/2] platform/x86: ISST: Return error during profile addition
commit: 4ff76db9d76cc13e83d60ea6650ee19ec97d0106
[2/2] platform/x86: ISST: Add a NULL check for sst_inst[]
commit: 47e50bee2a2cbb70b9a479c22c959a79857d9531
--
i.
prev parent reply other threads:[~2026-08-18 14:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 22:21 Srinivas Pandruvada
2026-08-11 22:21 ` [PATCH 1/2] platform/x86: ISST: Return error during profile addition Srinivas Pandruvada
2026-08-11 22:21 ` [PATCH 2/2] platform/x86: ISST: Add a NULL check for sst_inst[] Srinivas Pandruvada
2026-08-18 14:07 ` Ilpo Järvinen [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=178706206786.20251.8243742243633437618.b4-ty@b4 \
--to=ilpo.jarvinen@linux.intel.com \
--cc=hansg@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=sammiee5311@gmail.com \
--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
all inboxes | Powered by JetHome®