From: Mukesh Ojha <mojha@codeaurora.org>
To: Qian Cai <cai@lca.pw>,
mpe@ellerman.id.au, benh@kernel.crashing.org, paulus@samba.org
Cc: aik@ozlabs.ru, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powerpc/pseries/iommu: fix set but not used values
Date: Sun, 7 Apr 2019 12:04:10 +0530 [thread overview]
Message-ID: <ed223f2f-378b-1147-c482-6911f0e9941d@codeaurora.org> (raw)
In-Reply-To: <20190407024808.39821-1-cai@lca.pw>
On 4/7/2019 8:18 AM, Qian Cai wrote:
> The commit b7d6bf4fdd47 ("powerpc/pseries/pci: Remove obsolete SW
> invalidate") left 2 variables unused.
>
> arch/powerpc/platforms/pseries/iommu.c: In function 'tce_build_pSeries':
> arch/powerpc/platforms/pseries/iommu.c:108:17: warning: variable 'tces'
> set but not used [-Wunused-but-set-variable]
> __be64 *tcep, *tces;
> ^~~~
> arch/powerpc/platforms/pseries/iommu.c: In function 'tce_free_pSeries':
> arch/powerpc/platforms/pseries/iommu.c:132:17: warning: variable 'tces'
> set but not used [-Wunused-but-set-variable]
> __be64 *tcep, *tces;
> ^~~~
>
> Also, the commit 68c0449ea16d ("powerpc/pseries/iommu: Use memory@ nodes
> in max RAM address calculation") set "ranges" in
> ddw_memory_hotplug_max() but never use it.
>
> arch/powerpc/platforms/pseries/iommu.c: In function
> 'ddw_memory_hotplug_max':
> arch/powerpc/platforms/pseries/iommu.c:948:7: warning: variable 'ranges'
> set but not used [-Wunused-but-set-variable]
> int ranges, n_mem_addr_cells, n_mem_size_cells, len;
> ^~~~~~
>
> Signed-off-by: Qian Cai <cai@lca.pw>
Reviewed-by: Mukesh Ojha <mojha@codeaurora.org>
Cheers,
-Mukesh
> ---
> arch/powerpc/platforms/pseries/iommu.c | 13 +++++--------
> 1 file changed, 5 insertions(+), 8 deletions(-)
>
> diff --git a/arch/powerpc/platforms/pseries/iommu.c b/arch/powerpc/platforms/pseries/iommu.c
> index 36eb1ddbac69..03bbb299320e 100644
> --- a/arch/powerpc/platforms/pseries/iommu.c
> +++ b/arch/powerpc/platforms/pseries/iommu.c
> @@ -105,7 +105,7 @@ static int tce_build_pSeries(struct iommu_table *tbl, long index,
> unsigned long attrs)
> {
> u64 proto_tce;
> - __be64 *tcep, *tces;
> + __be64 *tcep;
> u64 rpn;
>
> proto_tce = TCE_PCI_READ; // Read allowed
> @@ -113,7 +113,7 @@ static int tce_build_pSeries(struct iommu_table *tbl, long index,
> if (direction != DMA_TO_DEVICE)
> proto_tce |= TCE_PCI_WRITE;
>
> - tces = tcep = ((__be64 *)tbl->it_base) + index;
> + tcep = ((__be64 *)tbl->it_base) + index;
>
> while (npages--) {
> /* can't move this out since we might cross MEMBLOCK boundary */
> @@ -129,9 +129,9 @@ static int tce_build_pSeries(struct iommu_table *tbl, long index,
>
> static void tce_free_pSeries(struct iommu_table *tbl, long index, long npages)
> {
> - __be64 *tcep, *tces;
> + __be64 *tcep;
>
> - tces = tcep = ((__be64 *)tbl->it_base) + index;
> + tcep = ((__be64 *)tbl->it_base) + index;
>
> while (npages--)
> *(tcep++) = 0;
> @@ -945,7 +945,7 @@ static phys_addr_t ddw_memory_hotplug_max(void)
>
> for_each_node_by_type(memory, "memory") {
> unsigned long start, size;
> - int ranges, n_mem_addr_cells, n_mem_size_cells, len;
> + int n_mem_addr_cells, n_mem_size_cells, len;
> const __be32 *memcell_buf;
>
> memcell_buf = of_get_property(memory, "reg", &len);
> @@ -955,9 +955,6 @@ static phys_addr_t ddw_memory_hotplug_max(void)
> n_mem_addr_cells = of_n_addr_cells(memory);
> n_mem_size_cells = of_n_size_cells(memory);
>
> - /* ranges in cell */
> - ranges = (len >> 2) / (n_mem_addr_cells + n_mem_size_cells);
> -
> start = of_read_number(memcell_buf, n_mem_addr_cells);
> memcell_buf += n_mem_addr_cells;
> size = of_read_number(memcell_buf, n_mem_size_cells);
next prev parent reply other threads:[~2019-04-07 6:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-07 2:48 [PATCH] powerpc/pseries/iommu: fix set but not used values Qian Cai
2019-04-07 6:34 ` Mukesh Ojha [this message]
2019-04-21 14:19 ` Michael Ellerman
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=ed223f2f-378b-1147-c482-6911f0e9941d@codeaurora.org \
--to=mojha@codeaurora.org \
--cc=aik@ozlabs.ru \
--cc=benh@kernel.crashing.org \
--cc=cai@lca.pw \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.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