From: Markus Elfring <Markus.Elfring@web.de>
To: "Anand Moon" <linux.amoon@gmail.com>,
linux-pci@vger.kernel.org, "Bjorn Helgaas" <bhelgaas@google.com>,
"Conor Dooley" <conor.dooley@microchip.com>,
"Kevin Xie" <kevin.xie@starfivetech.com>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
"Rob Herring" <robh@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Minda Chen <minda.chen@starfivetech.com>
Subject: Re: [PATCH] PCI: starfive: Fix kmemleak in StarFive PCIe driver's IRQ handling
Date: Sat, 8 Feb 2025 17:33:39 +0100 [thread overview]
Message-ID: <4195480d-f2f3-41ad-a035-c81e8f2ab0f4@web.de> (raw)
In-Reply-To: <20250208140110.2389-1-linux.amoon@gmail.com>
…
> This patch addresses a kmemleak reported during StarFive PCIe driver
…
> This patch introduces an event IRQ handler and the necessary
> infrastructure to manage these IRQs, preventing the memory leak.
See also:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.13#n94
Regards,
Markus
next prev parent reply other threads:[~2025-02-08 16:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-08 14:01 [PATCH v1] PCI: starfive: Fix kmemleak in StarFive PCIe driver's IRQ handling Anand Moon
2025-02-08 16:33 ` Markus Elfring [this message]
2025-02-09 4:22 ` [PATCH] " Anand Moon
2025-02-10 17:44 ` [PATCH v1] " Manivannan Sadhasivam
2025-02-10 19:39 ` Anand Moon
2025-02-14 6:09 ` Manivannan Sadhasivam
2025-02-20 8:13 ` Anand Moon
2025-02-20 10:23 ` Anand Moon
2025-02-24 8:01 ` Manivannan Sadhasivam
2025-02-24 10:08 ` Anand Moon
2025-02-24 11:54 ` Manivannan Sadhasivam
2025-02-24 14:03 ` Anand Moon
2025-02-24 14:41 ` Manivannan Sadhasivam
2025-02-24 16:07 ` Anand Moon
2025-03-03 15:23 ` Manivannan Sadhasivam
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=4195480d-f2f3-41ad-a035-c81e8f2ab0f4@web.de \
--to=markus.elfring@web.de \
--cc=bhelgaas@google.com \
--cc=conor.dooley@microchip.com \
--cc=kevin.xie@starfivetech.com \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux.amoon@gmail.com \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=minda.chen@starfivetech.com \
--cc=robh@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