Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1710531 > unrolled thread

[PATCH] powerpc: store the intended structure

Started byJulia Lawall <Julia.Lawall@lip6.fr>
First post2017-08-13 16:00 +0200
Last post2017-08-16 14:40 +0200
Articles 5 — 5 participants

Back to article view | Back to linux.kernel


Contents

  [PATCH] powerpc: store the intended structure Julia Lawall <Julia.Lawall@lip6.fr> - 2017-08-13 16:00 +0200
    Re: [PATCH] powerpc: store the intended structure Joe Perches <joe@perches.com> - 2017-08-13 16:40 +0200
      Re: [PATCH] powerpc: store the intended structure Julia Lawall <julia.lawall@lip6.fr> - 2017-08-13 16:50 +0200
    Re: [PATCH] powerpc: store the intended structure Michael Ellerman <mpe@ellerman.id.au> - 2017-08-15 13:20 +0200
    Re: powerpc: store the intended structure Michael Ellerman <patch-notifications@ellerman.id.au> - 2017-08-16 14:40 +0200

#1710531 — [PATCH] powerpc: store the intended structure

FromJulia Lawall <Julia.Lawall@lip6.fr>
Date2017-08-13 16:00 +0200
Subject[PATCH] powerpc: store the intended structure
Message-ID<ue1AR-7S4-15@gated-at.bofh.it>
Normally the values in the resource field and the argument to ARRAY_SIZE
in the num_resources are the same.  In this case, the value in the reousrce
field is the same as the one in the previous platform_device structure, and
appears to be a copy-paste error.  Replace the value in the resource field
with the argument to the local call to ARRAY_SIZE.

Signed-off-by: Julia Lawall <Julia.Lawall@lip6.fr>

---
 arch/powerpc/platforms/chrp/pegasos_eth.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/powerpc/platforms/chrp/pegasos_eth.c b/arch/powerpc/platforms/chrp/pegasos_eth.c
index 2b4dc6a..1976071 100644
--- a/arch/powerpc/platforms/chrp/pegasos_eth.c
+++ b/arch/powerpc/platforms/chrp/pegasos_eth.c
@@ -63,7 +63,7 @@
 	.name		= "orion-mdio",
 	.id		= -1,
 	.num_resources	= ARRAY_SIZE(mv643xx_eth_mvmdio_resources),
-	.resource	= mv643xx_eth_shared_resources,
+	.resource	= mv643xx_eth_mvmdio_resources,
 };
 
 static struct resource mv643xx_eth_port1_resources[] = {

[toc] | [next] | [standalone]


#1710538

FromJoe Perches <joe@perches.com>
Date2017-08-13 16:40 +0200
Message-ID<ue2dz-8jJ-3@gated-at.bofh.it>
In reply to#1710531
On Sun, 2017-08-13 at 15:24 +0200, Julia Lawall wrote:
> Normally the values in the resource field and the argument to ARRAY_SIZE
> in the num_resources are the same.  In this case, the value in the reousrce
> field is the same as the one in the previous platform_device structure, and
> appears to be a copy-paste error.  Replace the value in the resource field
> with the argument to the local call to ARRAY_SIZE.

found by a script or eyeballs?

[toc] | [prev] | [next] | [standalone]


#1710543

FromJulia Lawall <julia.lawall@lip6.fr>
Date2017-08-13 16:50 +0200
Message-ID<ue2nf-8n0-11@gated-at.bofh.it>
In reply to#1710538

On Sun, 13 Aug 2017, Joe Perches wrote:

> On Sun, 2017-08-13 at 15:24 +0200, Julia Lawall wrote:
> > Normally the values in the resource field and the argument to ARRAY_SIZE
> > in the num_resources are the same.  In this case, the value in the reousrce
> > field is the same as the one in the previous platform_device structure, and
> > appears to be a copy-paste error.  Replace the value in the resource field
> > with the argument to the local call to ARRAY_SIZE.
>
> found by a script or eyeballs?

A script that was looking for something else.  But I wrote a script for
this specific issue and this was the only match.  I am currently checking
in a more general way.

julia

[toc] | [prev] | [next] | [standalone]


#1712081

FromMichael Ellerman <mpe@ellerman.id.au>
Date2017-08-15 13:20 +0200
Message-ID<ueI38-An-11@gated-at.bofh.it>
In reply to#1710531
Julia Lawall <Julia.Lawall@lip6.fr> writes:

> Normally the values in the resource field and the argument to ARRAY_SIZE
> in the num_resources are the same.  In this case, the value in the reousrce
> field is the same as the one in the previous platform_device structure, and
> appears to be a copy-paste error.  Replace the value in the resource field
> with the argument to the local call to ARRAY_SIZE.
>
> Signed-off-by: Julia Lawall <Julia.Lawall@lip6.fr>
>
> ---
>  arch/powerpc/platforms/chrp/pegasos_eth.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Thanks. This is close to EOL code I think, but I'll merge it anyway as
it seems obviously correct.

cheers

> diff --git a/arch/powerpc/platforms/chrp/pegasos_eth.c b/arch/powerpc/platforms/chrp/pegasos_eth.c
> index 2b4dc6a..1976071 100644
> --- a/arch/powerpc/platforms/chrp/pegasos_eth.c
> +++ b/arch/powerpc/platforms/chrp/pegasos_eth.c
> @@ -63,7 +63,7 @@
>  	.name		= "orion-mdio",
>  	.id		= -1,
>  	.num_resources	= ARRAY_SIZE(mv643xx_eth_mvmdio_resources),
> -	.resource	= mv643xx_eth_shared_resources,
> +	.resource	= mv643xx_eth_mvmdio_resources,
>  };
>  
>  static struct resource mv643xx_eth_port1_resources[] = {

[toc] | [prev] | [next] | [standalone]


#1712913 — Re: powerpc: store the intended structure

FromMichael Ellerman <patch-notifications@ellerman.id.au>
Date2017-08-16 14:40 +0200
SubjectRe: powerpc: store the intended structure
Message-ID<uf5M6-73I-15@gated-at.bofh.it>
In reply to#1710531
On Sun, 2017-08-13 at 13:24:23 UTC, Julia Lawall wrote:
> Normally the values in the resource field and the argument to ARRAY_SIZE
> in the num_resources are the same.  In this case, the value in the reousrce
> field is the same as the one in the previous platform_device structure, and
> appears to be a copy-paste error.  Replace the value in the resource field
> with the argument to the local call to ARRAY_SIZE.
> 
> Signed-off-by: Julia Lawall <Julia.Lawall@lip6.fr>

Applied to powerpc next, thanks.

https://git.kernel.org/powerpc/c/36992606eee8016c36ad2576687e97

cheers

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web