From: "Jingoo Han" <jingoohan1@gmail.com>
To: "'Joao Pinto'" <Joao.Pinto@synopsys.com>,
"'Carlos Palminha'" <CARLOS.PALMINHA@synopsys.com>,
<linux-pci@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <bhelgaas@google.com>
Subject: Re: [PATCH] PCI: dwc: designware: make dw_pcie_prog_*_atu_unroll() static
Date: Mon, 17 Jul 2017 15:34:48 -0400 [thread overview]
Message-ID: <000c01d2ff33$c1202510$43606f30$@gmail.com> (raw)
In-Reply-To: <18cf8549-c1c6-bed2-60f2-202abc06d6b3@synopsys.com>
On Monday, July 17, 2017 9:28 AM, Joao Pinto wrote:
>=20
>=20
> Hi Carlos,
>=20
> =C3=80s 2:13 PM de 7/17/2017, Carlos Palminha escreveu:
> > Helper functions dw_pcie_prog_*_atu_unroll don't need to be in =
global
> scope,
> > so make it static.
> >
> > Cleans up sparse warnings:
> > - symbol 'dw_pcie_prog_outbound_atu_unroll' was not declared. Should =
it
> be static?
> > - symbol 'dw_pcie_prog_inbound_atu_unroll' was not declared. Should =
it
> be static?
> >
> > Signed-off-by: Carlos Palminha <palminha@synopsys.com>
> > ---
> > Patch made against linux-next tree, tag next-20170714
> >
> > drivers/pci/dwc/pcie-designware.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/pci/dwc/pcie-designware.c =
b/drivers/pci/dwc/pcie-
> designware.c
> > index 0e03af279259..48d6d0712ea8 100644
> > --- a/drivers/pci/dwc/pcie-designware.c
> > +++ b/drivers/pci/dwc/pcie-designware.c
> > @@ -107,7 +107,7 @@ static void dw_pcie_writel_ob_unroll(struct =
dw_pcie
> *pci, u32 index, u32 reg,
> > dw_pcie_writel_dbi(pci, offset + reg, val);
> > }
> >
> > -void dw_pcie_prog_outbound_atu_unroll(struct dw_pcie *pci, int =
index,
> int type,
> > +static void dw_pcie_prog_outbound_atu_unroll(struct dw_pcie *pci, =
int
> index, int type,
> > u64 cpu_addr, u64 pci_addr, u32 size)
> > {
> > u32 retries, val;
> > @@ -200,7 +200,7 @@ static void dw_pcie_writel_ib_unroll(struct =
dw_pcie
> *pci, u32 index, u32 reg,
> > dw_pcie_writel_dbi(pci, offset + reg, val);
> > }
> >
> > -int dw_pcie_prog_inbound_atu_unroll(struct dw_pcie *pci, int index, =
int
> bar,
> > +static int dw_pcie_prog_inbound_atu_unroll(struct dw_pcie *pci, int
> index, int bar,
> > u64 cpu_addr, enum dw_pcie_as_type as_type)
> > {
> > int type;
> > --
> > 2.11.0
> >
>=20
> That indeed escaped in the refactoring :) Thanks!
>=20
> Acked-by: Joao Pinto <jpinto@synopsys.com>
Acked-by: Jingoo Han <jingoohan1@gmail.com>
Best regards,
Jingoo Han
WARNING: multiple messages have this Message-ID (diff)
From: "Jingoo Han" <jingoohan1@gmail.com>
To: "'Joao Pinto'" <Joao.Pinto@synopsys.com>,
"'Carlos Palminha'" <CARLOS.PALMINHA@synopsys.com>,
<linux-pci@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <bhelgaas@google.com>
Subject: Re: [PATCH] PCI: dwc: designware: make dw_pcie_prog_*_atu_unroll() static
Date: Mon, 17 Jul 2017 15:34:48 -0400 [thread overview]
Message-ID: <000c01d2ff33$c1202510$43606f30$@gmail.com> (raw)
In-Reply-To: <18cf8549-c1c6-bed2-60f2-202abc06d6b3@synopsys.com>
On Monday, July 17, 2017 9:28 AM, Joao Pinto wrote:
>
>
> Hi Carlos,
>
> Às 2:13 PM de 7/17/2017, Carlos Palminha escreveu:
> > Helper functions dw_pcie_prog_*_atu_unroll don't need to be in global
> scope,
> > so make it static.
> >
> > Cleans up sparse warnings:
> > - symbol 'dw_pcie_prog_outbound_atu_unroll' was not declared. Should it
> be static?
> > - symbol 'dw_pcie_prog_inbound_atu_unroll' was not declared. Should it
> be static?
> >
> > Signed-off-by: Carlos Palminha <palminha@synopsys.com>
> > ---
> > Patch made against linux-next tree, tag next-20170714
> >
> > drivers/pci/dwc/pcie-designware.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/pci/dwc/pcie-designware.c b/drivers/pci/dwc/pcie-
> designware.c
> > index 0e03af279259..48d6d0712ea8 100644
> > --- a/drivers/pci/dwc/pcie-designware.c
> > +++ b/drivers/pci/dwc/pcie-designware.c
> > @@ -107,7 +107,7 @@ static void dw_pcie_writel_ob_unroll(struct dw_pcie
> *pci, u32 index, u32 reg,
> > dw_pcie_writel_dbi(pci, offset + reg, val);
> > }
> >
> > -void dw_pcie_prog_outbound_atu_unroll(struct dw_pcie *pci, int index,
> int type,
> > +static void dw_pcie_prog_outbound_atu_unroll(struct dw_pcie *pci, int
> index, int type,
> > u64 cpu_addr, u64 pci_addr, u32 size)
> > {
> > u32 retries, val;
> > @@ -200,7 +200,7 @@ static void dw_pcie_writel_ib_unroll(struct dw_pcie
> *pci, u32 index, u32 reg,
> > dw_pcie_writel_dbi(pci, offset + reg, val);
> > }
> >
> > -int dw_pcie_prog_inbound_atu_unroll(struct dw_pcie *pci, int index, int
> bar,
> > +static int dw_pcie_prog_inbound_atu_unroll(struct dw_pcie *pci, int
> index, int bar,
> > u64 cpu_addr, enum dw_pcie_as_type as_type)
> > {
> > int type;
> > --
> > 2.11.0
> >
>
> That indeed escaped in the refactoring :) Thanks!
>
> Acked-by: Joao Pinto <jpinto@synopsys.com>
Acked-by: Jingoo Han <jingoohan1@gmail.com>
Best regards,
Jingoo Han
next prev parent reply other threads:[~2017-07-17 19:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-17 13:13 [PATCH] PCI: dwc: designware: make dw_pcie_prog_*_atu_unroll() static Carlos Palminha
2017-07-17 13:27 ` Joao Pinto
2017-07-17 19:34 ` Jingoo Han [this message]
2017-07-17 19:34 ` Jingoo Han
2017-08-02 21:50 ` Bjorn Helgaas
2017-08-03 8:51 ` Carlos Palminha
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='000c01d2ff33$c1202510$43606f30$@gmail.com' \
--to=jingoohan1@gmail.com \
--cc=CARLOS.PALMINHA@synopsys.com \
--cc=Joao.Pinto@synopsys.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.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 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.