From: Choong Yong Liang <yong.liang.choong@linux.intel.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Andy Shevchenko" <andy.shevchenko@gmail.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
David E Box <david.e.box@linux.intel.com>,
platform-driver-x86@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] platform/x86: intel_pmc_ipc: add option to build without ACPI
Date: Mon, 17 Mar 2025 15:31:23 +0800 [thread overview]
Message-ID: <f02b9127-fec1-49c7-9cc1-f286cc3adca7@linux.intel.com> (raw)
In-Reply-To: <2a00773a-b887-7966-36de-0e2b93359912@linux.intel.com>
On 14/3/2025 7:56 pm, Ilpo Järvinen wrote:
> Hi both,
>
> The original commit went through net-next tree so I cannot take this into
> pdx86 tree until after the merge window. It seems low impact enough that
> coordinating with the netdev might not be worth the effort.
>
> To get it going through net-next tree, you'd need to submit v3 so that in
> addition to the current receipients, all relevant netdev people & ML are
> included as receipients. But I'd be fine if you leave it until after the
> merge window and I can then handle it then.
>
Hi Ilpo,
I believe we can leave the patch until after the merge window.
This approach would simplify the merging process without needing assistance
from the netdev maintainer for the platform code.
Thank you for your support.
next prev parent reply other threads:[~2025-03-17 7:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-13 8:55 Choong Yong Liang
2025-03-13 15:57 ` Andy Shevchenko
2025-03-14 11:56 ` Ilpo Järvinen
2025-03-17 7:31 ` Choong Yong Liang [this message]
2025-04-07 11:51 ` Ilpo Järvinen
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=f02b9127-fec1-49c7-9cc1-f286cc3adca7@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
all inboxes | Powered by JetHome®