mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: mario.limonciello@amd.com, Kuan-Wei Chiu <visitorckw@gmail.com>
Cc: perry.yuan@amd.com, hansg@kernel.org, jserv@ccns.ncku.edu.tw,
	 platform-driver-x86@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] platform/x86/amd: hfi: A couple of cleanups
Date: Wed, 15 Oct 2025 13:19:26 +0300	[thread overview]
Message-ID: <176052356672.21241.5215291958361985877.b4-ty@linux.intel.com> (raw)
In-Reply-To: <20251011063837.2318535-1-visitorckw@gmail.com>

On Sat, 11 Oct 2025 14:38:35 +0800, Kuan-Wei Chiu wrote:

> This patch series provides a couple of cleanups for the AMD HFI driver
> by removing unused and redundant code.
> 
> The changes remove an unused cpumask field from the amd_hfi_cpuinfo
> struct, along with a boilerplate .owner assignment that is already
> handled by the driver core and was flagged by coccicheck.
> 
> [...]


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.

The list of commits applied:
[1/2] platform/x86/amd: hfi: Remove unused cpumask from cpuinfo struct
      commit: 32647324c77012b7aed7ef48752909510d3c7ec7
[2/2] platform/x86/amd: hfi: Remove redundant assignment to .owner
      commit: 0254329897495c42646144376230add710078937

--
 i.


      parent reply	other threads:[~2025-10-15 10:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-11  6:38 Kuan-Wei Chiu
2025-10-11  6:38 ` [PATCH 1/2] platform/x86/amd: hfi: Remove unused cpumask from cpuinfo struct Kuan-Wei Chiu
2025-10-13 18:52   ` Mario Limonciello
2025-10-11  6:38 ` [PATCH 2/2] platform/x86/amd: hfi: Remove redundant assignment to .owner Kuan-Wei Chiu
2025-10-13 18:53   ` Mario Limonciello
2025-10-15 10:19 ` 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=176052356672.21241.5215291958361985877.b4-ty@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=hansg@kernel.org \
    --cc=jserv@ccns.ncku.edu.tw \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mario.limonciello@amd.com \
    --cc=perry.yuan@amd.com \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=visitorckw@gmail.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®