mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Shyam Sundar S K <Shyam-sundar.S-k@amd.com>,
	 Hans de Goede <hansg@kernel.org>,
	Sanket Goswami <Sanket.Goswami@amd.com>,
	 "Mario Limonciello (AMD)" <superm1@kernel.org>,
	Rong Zhang <i@rong.moe>
Cc: platform-driver-x86@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] platform/x86/amd/pmf: Clean up undesirable function outlining
Date: Thu, 08 Oct 2026 20:37:09 +0300	[thread overview]
Message-ID: <179148102914.29028.5928287984821543239.b4-ty@b4> (raw)
In-Reply-To: <20260901-amd-pmf-fix-outlining-v1-0-b54ff94d3d45@rong.moe>

On Tue, 01 Sep 2026 23:02:10 +0800, Rong Zhang wrote:

> The amd-pmf driver is notably bloated due to undesirable function
> outlining and linkage. Simple and dump helper functions as well as
> wrappers should really be static inline functions instead of global ones
> from the very beginning, or else they are prone to the overhead of
> function outlining and linkage, which bloats themselves and their
> callers.
> 
> [...]

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/5] platform/x86/amd/pmf: Inline !AMD_PMF_DEBUG stub
      commit: b8f7b92fcbd7e5801bbd18a42a9c10ef03e2ec35
[2/5] platform/x86/amd/pmf: Inline simple helper functions of Core Layer
      commit: c78d7b826cfc1642c78f5022b5acbf5ef09d88f9
[3/5] platform/x86/amd/pmf: Inline simple helper function of SPS Layer
      commit: 079cbf13340688ef697252b18bab9533acba3ecb
[4/5] platform/x86/amd/pmf: Inline simple helper function of Smart PC TA interfaces
      commit: ef1e7071c1f2832f3a7001be7f7c04bd872c14ae
[5/5] platform/x86/amd/pmf: Inline wrappers of ap{mf,ts}_if_call_store_buffer()
      commit: b21ebc6638d56f6007aff1fe93c5838dc138a364

--
 i.


      parent reply	other threads:[~2026-10-08 17:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-01 15:02 Rong Zhang
2026-09-01 15:02 ` [PATCH 1/5] platform/x86/amd/pmf: Inline !AMD_PMF_DEBUG stub Rong Zhang
2026-09-01 15:02 ` [PATCH 2/5] platform/x86/amd/pmf: Inline simple helper functions of Core Layer Rong Zhang
2026-09-01 15:02 ` [PATCH 3/5] platform/x86/amd/pmf: Inline simple helper function of SPS Layer Rong Zhang
2026-09-01 15:02 ` [PATCH 4/5] platform/x86/amd/pmf: Inline simple helper function of Smart PC TA interfaces Rong Zhang
2026-09-01 15:02 ` [PATCH 5/5] platform/x86/amd/pmf: Inline wrappers of ap{mf,ts}_if_call_store_buffer() Rong Zhang
2026-09-01 15:09 ` [PATCH 0/5] platform/x86/amd/pmf: Clean up undesirable function outlining Mario Limonciello
2026-09-19 15:18 ` Rong Zhang
2026-09-30 17:28   ` Shyam Sundar S K
2026-10-08 17:37 ` 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=179148102914.29028.5928287984821543239.b4-ty@b4 \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=Sanket.Goswami@amd.com \
    --cc=Shyam-sundar.S-k@amd.com \
    --cc=hansg@kernel.org \
    --cc=i@rong.moe \
    --cc=linux-kernel@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=superm1@kernel.org \
    /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®