Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Pratyush Anand <pratyush.anand@gmail.com>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	PCI <linux-pci@vger.kernel.org>
Subject: Re: of_match[] warnings
Date: Thu, 1 Oct 2020 11:50:37 -0500	[thread overview]
Message-ID: <20201001165037.GA2702236@bjorn-Precision-5520> (raw)
In-Reply-To: <CAL_JsqKKhN26qJT50zwaqtFDeUJBPJk0bRrGnFAz4k9K6f_Lhw@mail.gmail.com>

On Thu, Oct 01, 2020 at 11:43:12AM -0500, Rob Herring wrote:
> On Thu, Oct 1, 2020 at 10:53 AM Bjorn Helgaas <helgaas@kernel.org> wrote:
> >
> > On Thu, Oct 01, 2020 at 07:48:23AM -0500, Rob Herring wrote:
> > > On Wed, Sep 30, 2020 at 5:37 PM Bjorn Helgaas <helgaas@kernel.org> wrote:
> > > >
> > > > These warnings are sort of annoying.  I guess most of the other
> > > > drivers avoid this by depending on OF as well as COMPILE_TEST.
> > >
> > > Using the of_match_ptr() macro should prevent this.
> >
> > Both drivers *do* use of_match_ptr(), but the of_device_id table is
> > unused when of_match_ptr() throws away the pointer.
> 
> Oh right, it's actually we don't want to use of_match_ptr() in this case.
> 
> > I guess we could add __maybe_unused to squelch the warning.  Ugly, but
> > I do think COMPILE_TEST has some value.
> 
> We do that or an ifdef for drivers that actually work for !OF.
> 
> We also have lot's of 'depends on OF' as proposed too, but that's not
> really my preference given we have empty functions for most
> everything.

So just removing of_match_ptr() as below?  That seems way nicer than
any of the #ifdef, __maybe_unused, or "depends on OF" options.

diff --git a/drivers/pci/controller/dwc/pcie-spear13xx.c b/drivers/pci/controller/dwc/pcie-spear13xx.c
index 62846562da0b..b2ef8ffde79e 100644
--- a/drivers/pci/controller/dwc/pcie-spear13xx.c
+++ b/drivers/pci/controller/dwc/pcie-spear13xx.c
@@ -303,7 +303,7 @@ static struct platform_driver spear13xx_pcie_driver = {
 	.probe		= spear13xx_pcie_probe,
 	.driver = {
 		.name	= "spear-pcie",
-		.of_match_table = of_match_ptr(spear13xx_pcie_of_match),
+		.of_match_table = spear13xx_pcie_of_match,
 		.suppress_bind_attrs = true,
 	},
 };

      reply	other threads:[~2020-10-01 16:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-30 22:37 of_match[] warnings Bjorn Helgaas
2020-10-01 12:48 ` Rob Herring
2020-10-01 15:53   ` Bjorn Helgaas
2020-10-01 16:43     ` Rob Herring
2020-10-01 16:50       ` Bjorn Helgaas [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=20201001165037.GA2702236@bjorn-Precision-5520 \
    --to=helgaas@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=pratyush.anand@gmail.com \
    --cc=robh@kernel.org \
    --cc=thomas.petazzoni@bootlin.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