netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@snapgear.com>
To: Sebastian Siewior <bigeasy@linutronix.de>
Cc: Jeff Garzik <jgarzik@pobox.com>,
	netdev@vger.kernel.org, uclinux-dev@uclinux.org
Subject: Re: [PATCH 1/5] fec: kill warnings
Date: Thu, 03 Apr 2008 16:30:48 +1000	[thread overview]
Message-ID: <47F47998.1080702@snapgear.com> (raw)
In-Reply-To: <20080402210103.046161355@linutronix.de>

Hi Sebastian,

Sebastian Siewior wrote:
> linux-2.6-mk68/drivers/net/fec.c: In function 'fec_enet_module_init':
> linux-2.6-mk68/drivers/net/fec.c:2627: warning: unused variable 'j'
> linux-2.6-mk68/drivers/net/fec.c: At top level:
> linux-2.6-mk68/drivers/net/fec.c:2136: warning: 'mii_link_interrupt' defined but not used
> 
> Signed-off-by: Sebastian Siewior <bigeasy@linutronix.de>
> --- a/drivers/net/fec.c
> +++ b/drivers/net/fec.c
> @@ -67,6 +67,11 @@
>  #define	FEC_MAX_PORTS	1
>  #endif
>  
> +#if defined(CONFIG_M523x) || defined(CONFIG_M527x) || defined(CONFIG_M528x) || \
> +	defined(CONFIG_M520x) || defined(CONFIG_M532x)
> +#define DONT_NEED_mii_link_interrupt

I think using normal positive logic would be clearer, eg:

   HAVE_mii_link_interupt

Very few of the boards I have come across with the FEC silicon
actually hook up the MII interrupt, so the list of devices that
have it will be smaller.

Regards
Greg



> +#endif
> +
>  /*
>   * Define the fixed address of the FEC hardware.
>   */
> @@ -1222,7 +1227,7 @@ static phy_info_t const * const phy_info
>  };
>  
>  /* ------------------------------------------------------------------------- */
> -#if !defined(CONFIG_M532x)
> +#ifndef DONT_NEED_mii_link_interrupt
>  #ifdef CONFIG_RPXCLASSIC
>  static void
>  mii_link_interrupt(void *dev_id);
> @@ -2126,6 +2131,7 @@ mii_discover_phy(uint mii_reg, struct ne
>  
>  /* This interrupt occurs when the PHY detects a link change.
>  */
> +#ifndef DONT_NEED_mii_link_interrupt
>  #ifdef CONFIG_RPXCLASSIC
>  static void
>  mii_link_interrupt(void *dev_id)
> @@ -2148,6 +2154,7 @@ mii_link_interrupt(int irq, void * dev_i
>  
>  	return IRQ_HANDLED;
>  }
> +#endif
>  
>  static int
>  fec_enet_open(struct net_device *dev)
> @@ -2624,7 +2631,7 @@ fec_stop(struct net_device *dev)
>  static int __init fec_enet_module_init(void)
>  {
>  	struct net_device *dev;
> -	int i, j, err;
> +	int i, err;
>  	DECLARE_MAC_BUF(mac);
>  
>  	printk("FEC ENET Version 0.2\n");
> 

-- 
------------------------------------------------------------------------
Greg Ungerer  --  Chief Software Dude       EMAIL:     gerg@snapgear.com
Secure Computing Corporation                PHONE:       +61 7 3435 2888
825 Stanley St,                             FAX:         +61 7 3891 3630
Woolloongabba, QLD, 4102, Australia         WEB: http://www.SnapGear.com

  reply	other threads:[~2008-04-03  6:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-02 20:58 [PATCH 0/5] fixup locking on m68knommu fec Sebastian Siewior
2008-04-02 20:58 ` [PATCH 3/5] m68knommu: fec typedef a function Sebastian Siewior
2008-04-02 20:58 ` [PATCH 5/5] m68knommu: dont allocate unused interrupts Sebastian Siewior
2008-04-03  6:47   ` Greg Ungerer
2008-04-03  7:43     ` Sebastian Siewior
2008-04-03  9:34       ` Greg Ungerer
2008-04-02 20:58 ` [PATCH 2/5] m68knommu: fec: small coding style cleanup Sebastian Siewior
2008-04-02 20:58 ` [PATCH 4/5] m68knommu: fec fixup locking Sebastian Siewior
2008-04-02 20:58 ` [PATCH 1/5] fec: kill warnings Sebastian Siewior
2008-04-03  6:30   ` Greg Ungerer [this message]
2008-04-03  7:44     ` Sebastian Siewior
2008-04-03  9:30       ` Greg Ungerer
2008-04-03  6:54 ` [PATCH 0/5] fixup locking on m68knommu fec Greg Ungerer
2008-04-03  7:52   ` Sebastian Siewior

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=47F47998.1080702@snapgear.com \
    --to=gerg@snapgear.com \
    --cc=bigeasy@linutronix.de \
    --cc=jgarzik@pobox.com \
    --cc=netdev@vger.kernel.org \
    --cc=uclinux-dev@uclinux.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;
as well as URLs for NNTP newsgroup(s).