All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alistair Francis <alistair@alistair23.me>
To: marek.vasut+renesas@gmail.com, yoshihiro.shimoda.uh@renesas.com,
	linux-pci@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Cc: lpieralisi@kernel.org, kw@linux.com, robh@kernel.org,
	bhelgaas@google.com, alistair23@gmail.com, dlemoal@kernel.org,
	Alistair Francis <alistair@alistair23.me>
Subject: [PATCH] PCI: rcar-ep: Include linux/pci-epf.h instead of linux/pci-epc.h
Date: Wed,  5 Jul 2023 20:48:24 +1000	[thread overview]
Message-ID: <20230705104824.174396-1-alistair@alistair23.me> (raw)

pci-epc.h doesn't define the members of the pci_epf_header struct, so
trying to access them results in errors like this:

    error: invalid use of undefined type 'struct pci_epf_header'
      167 |                 val = hdr->vendorid;

Instead let's include pci-epf.h which not only defines the
pci_epf_header but also includes pci-epc.h.

Signed-off-by: Alistair Francis <alistair@alistair23.me>
---
 drivers/pci/controller/pcie-rcar-ep.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/pci/controller/pcie-rcar-ep.c b/drivers/pci/controller/pcie-rcar-ep.c
index f9682df1da61..5afc91d11eef 100644
--- a/drivers/pci/controller/pcie-rcar-ep.c
+++ b/drivers/pci/controller/pcie-rcar-ep.c
@@ -10,7 +10,7 @@
 #include <linux/of_address.h>
 #include <linux/of_platform.h>
 #include <linux/pci.h>
-#include <linux/pci-epc.h>
+#include <linux/pci-epf.h>
 #include <linux/platform_device.h>
 #include <linux/pm_runtime.h>
 
-- 
2.40.1


             reply	other threads:[~2023-07-05 10:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-05 10:48 Alistair Francis [this message]
2023-07-05 11:10 ` [PATCH] PCI: rcar-ep: Include linux/pci-epf.h instead of linux/pci-epc.h Damien Le Moal
2023-07-05 11:44   ` Krzysztof Wilczyński
2023-07-05 11:57     ` Alistair Francis
2023-07-05 13:15       ` Krzysztof Wilczyński
2023-07-05 21:53         ` Damien Le Moal
2023-07-06  1:44         ` Alistair Francis

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=20230705104824.174396-1-alistair@alistair23.me \
    --to=alistair@alistair23.me \
    --cc=alistair23@gmail.com \
    --cc=bhelgaas@google.com \
    --cc=dlemoal@kernel.org \
    --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=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 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.