From: Frank Li <frank.li@nxp.com>
To: Tom Rix <trix@redhat.com>, "kishon@ti.com" <kishon@ti.com>,
"lpieralisi@kernel.org" <lpieralisi@kernel.org>,
"kw@linux.com" <kw@linux.com>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"jdmason@kudzu.us" <jdmason@kudzu.us>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"ntb@lists.linux.dev" <ntb@lists.linux.dev>
Subject: RE: [EXT] [PATCH v2] PCI: endpoint: reduce several globals to statics
Date: Thu, 30 Jun 2022 21:09:13 +0000 [thread overview]
Message-ID: <PAXPR04MB91864363B29A14331E2E8AFA88BA9@PAXPR04MB9186.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20220630210517.1825677-1-trix@redhat.com>
> -----Original Message-----
> From: Tom Rix <trix@redhat.com>
> Sent: Thursday, June 30, 2022 4:05 PM
> To: kishon@ti.com; lpieralisi@kernel.org; kw@linux.com;
> bhelgaas@google.com; Frank Li <frank.li@nxp.com>; jdmason@kudzu.us
> Cc: linux-pci@vger.kernel.org; linux-kernel@vger.kernel.org; Tom Rix
> <trix@redhat.com>
> Subject: [EXT] [PATCH v2] PCI: endpoint: reduce several globals to statics
Added ntb mail list ntb@lists.linux.dev
>
> Caution: EXT Email
>
> sparse reports
> drivers/pci/endpoint/functions/pci-epf-vntb.c:956:10: warning: symbol
> 'pci_space' was not declared. Should it be static?
> drivers/pci/endpoint/functions/pci-epf-vntb.c:975:5: warning: symbol
> 'pci_read' was not declared. Should it be static?
> drivers/pci/endpoint/functions/pci-epf-vntb.c:984:5: warning: symbol
> 'pci_write' was not declared. Should it be static?
> drivers/pci/endpoint/functions/pci-epf-vntb.c:989:16: warning: symbol
> 'vpci_ops' was not declared. Should it be static?
>
> These functions and variables are only used in pci-epf-vntb.c, so their storage
> class specifiers should be static.
>
> Fixes: ff32fac00d97 ("NTB: EPF: support NTB transfer between PCI RC and EP
> connection")
> Signed-off-by: Tom Rix <trix@redhat.com>
> ---
> v2 : Change commit prefix
Acked-by: Frank Li <Frank.Li@nxp.com>
>
> ---
> drivers/pci/endpoint/functions/pci-epf-vntb.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/pci/endpoint/functions/pci-epf-vntb.c
> b/drivers/pci/endpoint/functions/pci-epf-vntb.c
> index ebf7e243eefa..6f0775b1fec3 100644
> --- a/drivers/pci/endpoint/functions/pci-epf-vntb.c
> +++ b/drivers/pci/endpoint/functions/pci-epf-vntb.c
> @@ -953,7 +953,7 @@ static struct config_group *epf_ntb_add_cfs(struct
> pci_epf *epf,
>
> #define VPCI_BUS_NUM 0x10
>
> -uint32_t pci_space[] = {
> +static uint32_t pci_space[] = {
> (VNTB_VID | (VNTB_PID << 16)), //DeviceID, Vendor ID
> 0, // status, Command
> 0xffffffff, // Class code, subclass, prog if, revision id
> @@ -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,12 +981,12 @@ 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;
> }
>
> -struct pci_ops vpci_ops = {
> +static struct pci_ops vpci_ops = {
> .read = pci_read,
> .write = pci_write,
> };
> --
> 2.27.0
parent reply other threads:[~2022-06-30 21:09 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20220630210517.1825677-1-trix@redhat.com>]
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=PAXPR04MB91864363B29A14331E2E8AFA88BA9@PAXPR04MB9186.eurprd04.prod.outlook.com \
--to=frank.li@nxp.com \
--cc=bhelgaas@google.com \
--cc=jdmason@kudzu.us \
--cc=kishon@ti.com \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=ntb@lists.linux.dev \
--cc=trix@redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).