From: Ben Warren <biggerbadderben@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ppc4xx: Fixed compilation warning in 4xx_enet.c
Date: Mon, 20 Jul 2009 22:55:30 -0700 [thread overview]
Message-ID: <4A655852.7050103@gmail.com> (raw)
In-Reply-To: <ae0c01470907111156n39d799edr7b577276da6f2393@mail.gmail.com>
Stefan,
Can I get an ACK from you on this? Sorry if you already did and I missed it.
regards,
Ben
Alessio Centazzo wrote:
> This patch fixes a compilation warning for some Ethernet PHY-less
> PPC4xx platforms (440SPE based ones) and a potential compilation
> error for 440SP platforms (use of undefined 'ethgroup' variable).
> In the original code and in case of 440SPE platforms, 'ethgroup'
> is initialized to -1 and never modified. Later in the function,
> within an #ifdef statement, an 'if statement' executes code only
> if 'ethgroup' is set to 4, therefore it is harmless to avoid
> executing the 'if statement' by removing the CONFIG_440SPE from
> the affected #ifdefs. In case of 440SP platforms with on-board
> Ethernet PHY, 'ethgroup' is undefined but used (there are not such
> platforms in the repository yet). All other architectures are not
> affected by this change.
>
> Signed-off-by: Alessio Centazzo acpatin at yahoo.com
> ---
> drivers/net/4xx_enet.c | 3 +--
> 1 files changed, 1 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/4xx_enet.c b/drivers/net/4xx_enet.c
> index 587605d..c020048 100644
> --- a/drivers/net/4xx_enet.c
> +++ b/drivers/net/4xx_enet.c
> @@ -870,7 +870,7 @@ static int ppc_4xx_eth_init (struct eth_device
> *dev, bd_t * bis)
> defined(CONFIG_405EX)
> u32 opbfreq;
> sys_info_t sysinfo;
> -#if defined(CONFIG_440GX) || defined(CONFIG_440SPE) || \
> +#if defined(CONFIG_440GX) || \
> defined(CONFIG_440EPX) || defined(CONFIG_440GRX) || \
> defined(CONFIG_460EX) || defined(CONFIG_460GT) || \
> defined(CONFIG_405EX)
> @@ -1119,7 +1119,6 @@ static int ppc_4xx_eth_init (struct eth_device
> *dev, bd_t * bis)
>
> #if defined(CONFIG_440GX) || \
> defined(CONFIG_440EPX) || defined(CONFIG_440GRX) || \
> - defined(CONFIG_440SP) || defined(CONFIG_440SPE) || \
> defined(CONFIG_460EX) || defined(CONFIG_460GT) || \
> defined(CONFIG_405EX)
>
>
next prev parent reply other threads:[~2009-07-21 5:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-11 18:56 [U-Boot] [PATCH] ppc4xx: Fixed compilation warning in 4xx_enet.c Alessio Centazzo
2009-07-20 8:40 ` Stefan Roese
2009-07-21 5:55 ` Ben Warren [this message]
2009-07-21 6:52 ` Stefan Roese
2009-07-21 6:54 ` Ben Warren
-- strict thread matches above, loose matches on Subject: below --
2009-07-01 3:43 Alessio Centazzo
2009-07-01 7:21 ` Stefan Roese
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=4A655852.7050103@gmail.com \
--to=biggerbadderben@gmail.com \
--cc=u-boot@lists.denx.de \
/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.