From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Suma Hegde <suma.hegde@amd.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
platform-driver-x86@vger.kernel.org,
Naveen Krishna Chatradhi <nchatrad@amd.com>
Subject: Re: [PATCH v3 1/3] platform/x86/amd/hsmp: create plat specific struct
Date: Wed, 27 Sep 2023 14:18:16 +0300 (EEST) [thread overview]
Message-ID: <339fc252-4f46-171a-1b20-088c0651015@linux.intel.com> (raw)
In-Reply-To: <169573351745.5370.1730064995365398437.b4-ty@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1411 bytes --]
On Tue, 26 Sep 2023, Ilpo Järvinen wrote:
> On Tue, 19 Sep 2023 09:20:55 +0000, Suma Hegde wrote:
>
> > Having a separate platform device structure helps in future, to
> > contain platform specific variables and other data.
> >
> >
>
>
> 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.
>
> Once I've run some tests on the review-ilpo branch the patches
> there will be added to the platform-drivers-x86/for-next branch
> and eventually will be included in the pdx86 pull-request to
> Linus for the next merge-window.
>
> The list of commits applied:
> [1/3] platform/x86/amd/hsmp: create plat specific struct
> commit: 6448b90731aabbfb0e351b11be37af94c157dda4
> [2/3] platform/x86/amd/hsmp: add support for metrics tbl
> commit: 0f21042c11c7fa9053d5af1797f5a9380579f4dd
This ended up breaking the build and for some reason lkp had not caught it
(probably didn't build the series at all since the build fails already
with allyesconfig).
I'll fix this in review-ilpo branch for you but please try to build test
in the future to add a little bit of redundancy into build testing.
> [3/3] platform/x86/amd/hsmp: improve the error log
> commit: bd2b5ff0df3da9b75e684d99cd5b1ed4e74e24db
--
i.
prev parent reply other threads:[~2023-09-27 11:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 9:20 [PATCH v3 1/3] platform/x86/amd/hsmp: create plat specific struct Suma Hegde
2023-09-19 9:20 ` [PATCH v3 2/3] platform/x86/amd/hsmp: add support for metrics tbl Suma Hegde
2023-09-19 13:07 ` Ilpo Järvinen
2023-09-21 15:14 ` Hans de Goede
2023-09-22 8:56 ` Ilpo Järvinen
2023-09-26 8:20 ` Hans de Goede
2023-09-19 9:20 ` [PATCH v3 3/3] platform/x86/amd/hsmp: improve the error log Suma Hegde
2023-09-19 13:00 ` Ilpo Järvinen
2023-09-19 13:00 ` [PATCH v3 1/3] platform/x86/amd/hsmp: create plat specific struct Ilpo Järvinen
2023-09-26 13:05 ` Ilpo Järvinen
2023-09-27 11:18 ` 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=339fc252-4f46-171a-1b20-088c0651015@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=nchatrad@amd.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=suma.hegde@amd.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