From: Jon Mason <jdmason@kudzu.us>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Souptick Joarder <jrdr.linux@gmail.com>,
kishon@ti.com, lpieralisi@kernel.org, kw@linux.com,
bhelgaas@google.com, Frank.Li@nxp.com, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] NTB: EPF: Mark pci_read and pci_write as static
Date: Fri, 12 Aug 2022 10:14:21 -0400 [thread overview]
Message-ID: <YvZgPQGCFDDUPeTU@kudzu.us> (raw)
In-Reply-To: <20220712194936.GA790126@bhelgaas>
On Tue, Jul 12, 2022 at 02:49:36PM -0500, Bjorn Helgaas wrote:
> On Fri, Jul 08, 2022 at 07:30:35AM +0530, Souptick Joarder wrote:
> > From: "Souptick Joarder (HPE)" <jrdr.linux@gmail.com>
> >
> > kernel test robot throws below warning ->
> >
> > drivers/pci/endpoint/functions/pci-epf-vntb.c:975:5: warning:
> > no previous prototype for 'pci_read' [-Wmissing-prototypes]
> > drivers/pci/endpoint/functions/pci-epf-vntb.c:984:5: warning:
> > no previous prototype for 'pci_write' [-Wmissing-prototypes]
> >
> > mark them as static.
> >
> > Reported-by: kernel test robot <lkp@intel.com>
> > Signed-off-by: Souptick Joarder (HPE) <jrdr.linux@gmail.com>
>
> IIUC this series is going via Jon. Let me know if I need to do
> anything.
Sorry for the extremely long delay in response. This series is in my
ntb branch and will be in my pull request for v5.20 which should be
going out later today.
Thanks,
Jon
>
> > ---
> > drivers/pci/endpoint/functions/pci-epf-vntb.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/pci/endpoint/functions/pci-epf-vntb.c b/drivers/pci/endpoint/functions/pci-epf-vntb.c
> > index ebf7e243eefa..111568089d45 100644
> > --- a/drivers/pci/endpoint/functions/pci-epf-vntb.c
> > +++ b/drivers/pci/endpoint/functions/pci-epf-vntb.c
> > @@ -972,7 +972,7 @@ uint32_t pci_space[] = {
> > 0, //Max Lat, Min Gnt, interrupt pin, interrupt line
> > };
> >
> > -int pci_read(struct pci_bus *bus, unsigned int devfn, int where, int size, u32 *val)
> > +static int pci_read(struct pci_bus *bus, unsigned int devfn, int where, int size, u32 *val)
> > {
> > if (devfn == 0) {
> > memcpy(val, ((uint8_t *)pci_space) + where, size);
> > @@ -981,7 +981,7 @@ int pci_read(struct pci_bus *bus, unsigned int devfn, int where, int size, u32 *
> > return -1;
> > }
> >
> > -int pci_write(struct pci_bus *bus, unsigned int devfn, int where, int size, u32 val)
> > +static int pci_write(struct pci_bus *bus, unsigned int devfn, int where, int size, u32 val)
> > {
> > return 0;
> > }
> > --
> > 2.25.1
> >
prev parent reply other threads:[~2022-08-12 14:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 2:00 [PATCH] NTB: EPF: Mark pci_read and pci_write as static Souptick Joarder
2022-07-12 19:49 ` Bjorn Helgaas
2022-08-12 14:14 ` Jon Mason [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=YvZgPQGCFDDUPeTU@kudzu.us \
--to=jdmason@kudzu.us \
--cc=Frank.Li@nxp.com \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=jrdr.linux@gmail.com \
--cc=kishon@ti.com \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lpieralisi@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