From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: "Liu, Yongxin" <Yongxin.Liu@windriver.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"david.e.box@linux.intel.com" <david.e.box@linux.intel.com>,
"andrew@lunn.ch" <andrew@lunn.ch>,
"platform-driver-x86@vger.kernel.org"
<platform-driver-x86@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: RE: [PATCH net v2] platform/x86: intel_pmc_ipc: fix ACPI buffer memory leak
Date: Wed, 26 Nov 2025 11:50:10 +0200 (EET) [thread overview]
Message-ID: <6505d4a2-9d21-64ef-e07d-dabc7123c4c1@linux.intel.com> (raw)
In-Reply-To: <SJ0PR11MB50725E455D5B0089507E8311E5D1A@SJ0PR11MB5072.namprd11.prod.outlook.com>
On Tue, 25 Nov 2025, Liu, Yongxin wrote:
> > -----Original Message-----
> > From: Jakub Kicinski <kuba@kernel.org>
> > Sent: Tuesday, November 25, 2025 11:15
> > To: Liu, Yongxin <Yongxin.Liu@windriver.com>
> > Cc: linux-kernel@vger.kernel.org; netdev@vger.kernel.org;
> > david.e.box@linux.intel.com; ilpo.jarvinen@linux.intel.com; andrew@lunn.ch;
> > platform-driver-x86@vger.kernel.org; stable@vger.kernel.org
> > Subject: Re: [PATCH net v2] platform/x86: intel_pmc_ipc: fix ACPI buffer
> > memory leak
> >
> > CAUTION: This email comes from a non Wind River email account!
> > Do not click links or open attachments unless you recognize the sender and
> > know the content is safe.
> >
> > On Tue, 25 Nov 2025 03:07:30 +0000 Liu, Yongxin wrote:
> > > > -----Original Message-----
> > > > From: Jakub Kicinski <kuba@kernel.org>
> > > > Sent: Tuesday, November 25, 2025 10:56
> > > > To: Liu, Yongxin <Yongxin.Liu@windriver.com>
> > > > Cc: linux-kernel@vger.kernel.org; netdev@vger.kernel.org;
> > > > david.e.box@linux.intel.com; ilpo.jarvinen@linux.intel.com;
> > > > andrew@lunn.ch; platform-driver-x86@vger.kernel.org;
> > > > stable@vger.kernel.org
> > > > Subject: Re: [PATCH net v2] platform/x86: intel_pmc_ipc: fix ACPI
> > > > buffer memory leak
> > > >
> > > > CAUTION: This email comes from a non Wind River email account!
> > > > Do not click links or open attachments unless you recognize the
> > > > sender and know the content is safe.
> > > >
> > > > On Tue, 25 Nov 2025 10:29:53 +0800 yongxin.liu@windriver.com wrote:
> > > > > Subject: [PATCH net v2] platform/x86: intel_pmc_ipc: fix ACPI
> > > > > buffer
> > > > memory leak
> > > >
> > > > Presumably typo in the subject? Why would this go via netdev/net.. ?
> > >
> > > Because the only caller of intel_pmc_ipc() is
> > drivers/net/ethernet/stmicro/stmmac/dwmac-intel.c.
> > > I have sent both to the platform-driver-x86@vger.kernel.org and
> > netdev@vger.kernel.org mailing lists.
> >
> > Just to be clear -- the CC is fine, but given the code path - the platform
> > maintainer will likely take this via their tree. And the subject
> > designation is to indicate which maintainer you're expecting to process
> > the patch.
>
> Got it. If needed, I will resend with the correct subject.
Hi Yongxin,
As this code belongs to pdx86 domain, please ignore Andrew's feedback on
not using __free() (which was given with the assumption this would fall
under netdev's domain that applies a different rule).
Using cleanup.h helpers is required for new pdx86 code when it avoids
error handling gotos.
--
i.
prev parent reply other threads:[~2025-11-26 9:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 2:29 [PATCH net v2] platform/x86: intel_pmc_ipc: fix ACPI buffer memory leak yongxin.liu
2025-11-25 2:56 ` Jakub Kicinski
2025-11-25 3:07 ` Liu, Yongxin
2025-11-25 3:14 ` Jakub Kicinski
2025-11-25 3:28 ` Liu, Yongxin
2025-11-26 9:50 ` 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=6505d4a2-9d21-64ef-e07d-dabc7123c4c1@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=Yongxin.Liu@windriver.com \
--cc=andrew@lunn.ch \
--cc=david.e.box@linux.intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.