The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Choong Yong Liang <yong.liang.choong@linux.intel.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: "Hans de Goede" <hdegoede@redhat.com>,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
	"David E Box" <david.e.box@linux.intel.com>,
	platform-driver-x86@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] platform/x86: intel_pmc_ipc: add option to build without ACPI
Date: Wed, 12 Mar 2025 19:23:49 +0800	[thread overview]
Message-ID: <dbac683e-ab8d-440f-8013-f0ff2287a5ff@linux.intel.com> (raw)
In-Reply-To: <CAHp75VekTbp++4yw4yDhtB96K+C0w1uHiVih5x-jO+TWRLiPmw@mail.gmail.com>



On 12/3/2025 3:54 pm, Andy Shevchenko wrote:
> On Wed, Mar 12, 2025 at 4:30 AM Choong Yong Liang
> <yong.liang.choong@linux.intel.com> wrote:
> 
> Thank you, my comments below.
> 
>> This patch introduces a configuration option that allows users to
> 
> s/This patch introduces/Introduce/
> 
>> build the intel_pmc_ipc driver without ACPI support. This is useful
>> for systems where ACPI is not available or desired.
>>
>> Based on the discussion from the patch: https://patchwork.kernel.org/
>> project/netdevbpf/patch/20250227121522.1802832-6-
>> yong.liang.choong@linux.intel.com/#26280764, it was necessary to
>> provide this option to accommodate specific use cases.
> 
> Make it a Link tag, like
> 
> "...from the patch [1], it was..."
> 
> 
> Link: https://.... [1]
> 
> 
Hi Andy,

Thank you for your detailed feedback and suggestions. I'll make the 
necessary adjustments to the patch based on your comments above.

>> Signed-off-by: David E. Box <david.e.box@linux.intel.com>
>> Signed-off-by: Choong Yong Liang <yong.liang.choong@linux.intel.com>
> 
> This is wrong as either it's a wrong tag (SoB --> Suggested-by?), or
> missing Co-developed-by, or wrong order (but in that case David should
> have sent the patch).
> 
I believe the sequence is still correct, as the solution was provided by 
David, and he should be the main author. I'm just the submitter, so my 
sign-off should be placed last.
> ...
> 
>> +#if CONFIG_ACPI
> 
> Better to have #ifdef, but see below
> 
>>   static inline int intel_pmc_ipc(struct pmc_ipc_cmd *ipc_cmd, struct pmc_ipc_rbuf *rbuf)
>>   {
> 
>>   }
>> +#else
>> +static inline int intel_pmc_ipc(struct pmc_ipc_cmd *ipc_cmd, struct pmc_ipc_rbuf *rbuf)
>> +{ return -ENODEV; }
>> +#endif /* CONFIG_ACPI */
> 
> Since it's already static inline, it might be more natural to have
> this inside the function. The current is usually used for the C impl.
> + static inline stub, like
> 
> #ifdef FOO
> int foo(...);
> #else
> static inline int foo(...) { return ... }
> #endif
> 
> But I'm not insisting, it's up to the PDx86 maintainers.
> 
Sure, let's wait for more feedback.

  reply	other threads:[~2025-03-12 11:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-12  2:29 [PATCH v1] platform/x86: intel_pmc_ipc: add option to build without ACPI Choong Yong Liang
2025-03-12  7:54 ` Andy Shevchenko
2025-03-12 11:23   ` Choong Yong Liang [this message]
2025-03-12 14:00     ` Andy Shevchenko
2025-03-13  8:59       ` Choong Yong Liang

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=dbac683e-ab8d-440f-8013-f0ff2287a5ff@linux.intel.com \
    --to=yong.liang.choong@linux.intel.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=david.e.box@linux.intel.com \
    --cc=hdegoede@redhat.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=platform-driver-x86@vger.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