linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Marek Vasut <marek.vasut+renesas@gmail.com>,
	Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
Cc: "Liang He" <windhl@126.com>,
	"Geert Uytterhoeven" <geert+renesas@glider.be>,
	"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Wilczyński" <kw@linux.com>,
	linux-pci@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	"Bjorn Helgaas" <bhelgaas@google.com>
Subject: [PATCH 0/2] PCI: rcar: Fix of_find_matching_node() reference leak
Date: Tue, 21 Jun 2022 21:57:30 -0500	[thread overview]
Message-ID: <20220622025732.1359389-1-helgaas@kernel.org> (raw)

From: Bjorn Helgaas <bhelgaas@google.com>

Alternate proposal for Liang's patch [1].

This is a bulkier fix, but removes the redundant
rcar_pcie_abort_handler_of_match[] table.

It also simplifies the unusual device_initcall()/builtin_platform_driver() 
construct, which seems unnecessary as far as I can tell.

Compile-tested only.

[1] https://lore.kernel.org/r/20220621070145.4080147-1-windhl@126.com

Bjorn Helgaas (2):
  PCI: rcar: Add dev struct for of_device_get_match_data()
  PCI: rcar: Resolve of_find_matching_node() reference leak

 drivers/pci/controller/pcie-rcar-host.c | 113 +++++++++++++-----------
 1 file changed, 60 insertions(+), 53 deletions(-)

-- 
2.25.1


             reply	other threads:[~2022-06-22  2:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-22  2:57 Bjorn Helgaas [this message]
2022-06-22  2:57 ` [PATCH 1/2] PCI: rcar: Add dev struct for of_device_get_match_data() Bjorn Helgaas
2022-06-22  2:57 ` [PATCH 2/2] PCI: rcar: Resolve of_find_matching_node() reference leak Bjorn Helgaas
2022-06-22  7:45   ` Geert Uytterhoeven
2022-06-22 11:05     ` Bjorn Helgaas

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=20220622025732.1359389-1-helgaas@kernel.org \
    --to=helgaas@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=geert+renesas@glider.be \
    --cc=kw@linux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=marek.vasut+renesas@gmail.com \
    --cc=robh@kernel.org \
    --cc=windhl@126.com \
    --cc=yoshihiro.shimoda.uh@renesas.com \
    /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;
as well as URLs for NNTP newsgroup(s).