From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: rajvi.jingar@linux.intel.com,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org,
sathyanarayanan.kuppuswamy@linux.intel.com, hdegoede@redhat.com,
"David E. Box" <david.e.box@linux.intel.com>
Subject: Re: [PATCH V2 1/3] platform/x86/intel/vsec: Remove nuisance message
Date: Mon, 04 Mar 2024 15:16:57 +0200 [thread overview]
Message-ID: <170955821765.5357.6032325294708039590.b4-ty@linux.intel.com> (raw)
In-Reply-To: <20240227190134.1592072-1-david.e.box@linux.intel.com>
On Tue, 27 Feb 2024 11:01:32 -0800, David E. Box wrote:
> intel_vsec_walk_header() is used to configure features from devices that
> don't provide a PCI VSEC or DVSEC structure. Some of these features may
> be unsupported and fail to load. Ignore them silently as we do for
> unsupported features described by VSEC/DVSEC.
>
>
Thank you for your contribution, it has been applied to my local
review-ilpo branch. Note it will show up in the public
platform-drivers-x86/review-ilpo branch only once I've pushed my
local branch there, which might take a while.
The list of commits applied:
[1/3] platform/x86/intel/vsec: Remove nuisance message
commit: ad742f6580e1d50a5482fc4f2ed0d248fa784677
[2/3] platform/x86/intel/pmc/lnl: Remove SSRAM support
commit: 728720381879e9e0bc68ff9edca52261c1f5bc31
[3/3] platform/x86/intel/pmc/arl: Put GNA device in D3
commit: a5e28e2b384fe5c8fed36907cf4297d629612bdb
--
i.
prev parent reply other threads:[~2024-03-04 13:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 19:01 David E. Box
2024-02-27 19:01 ` [PATCH V2 2/3] platform/x86/intel/pmc/lnl: Remove SSRAM support David E. Box
2024-02-27 19:01 ` [PATCH V2 3/3] platform/x86/intel/pmc/arl: Put GNA device in D3 David E. Box
2024-02-27 19:54 ` Kuppuswamy Sathyanarayanan
2024-03-04 13:16 ` 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=170955821765.5357.6032325294708039590.b4-ty@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=david.e.box@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rajvi.jingar@linux.intel.com \
--cc=sathyanarayanan.kuppuswamy@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®