Home » Mailing list archives » linux-kernel » 2007 » October » 18

Re: [PATCH][NET] gianfar: fix obviously wrong #ifdef CONFIG_GFAR_NAPI placement

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
[view in full thread]
From: Andy Whitcroft <apw@...>
To: Anton Vorontsov <avorontsov@...>
Cc: <leoli@...>, <jgarzik@...>, <paulus@...>, <galak@...>, <afleming@...>, <linuxppc-dev@...>, <netdev@...>, <linux-kernel@...>
Subject: Re: [PATCH][NET] gianfar: fix obviously wrong #ifdef CONFIG_GFAR_NAPI placement
Date: Thursday, October 18, 2007 - 5:40 am

The check then is to see if a non {}'d block has no statements in it if the
ifdef is null.  Hmmm.  May be possible.  Will think on it.

        if (err)
+#ifdef CONFIG_GFAR_NAPI
                napi_disable(&priv->napi);
+#endif

-apw
-
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
Messages in current thread:
[PATCH][NET] gianfar: fix obviously wrong #ifdef CONFIG_GFAR..., Anton Vorontsov, (Wed Oct 17, 3:57 pm)
Re: [PATCH][NET] gianfar: fix obviously wrong #ifdef CONFIG_..., Andy Whitcroft, (Thu Oct 18, 5:40 am)
Re: [PATCH][NET] gianfar: fix obviously wrong #ifdef CONFIG_..., Jeff Garzik, (Wed Oct 17, 8:21 pm)