From: Jean Tourrilhes <jt@hpl.hp.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: jgarzik@pobox.com, netdev@oss.sgi.com
Subject: Re: [PATCH] (v2) arlan: remove gcc warning with CONFIG_PROC_FS=n
Date: Thu, 27 Jan 2005 08:47:05 -0800 [thread overview]
Message-ID: <20050127164705.GC747@bougret.hpl.hp.com> (raw)
In-Reply-To: <41F84605.5060501@osdl.org>
On Wed, Jan 26, 2005 at 05:38:13PM -0800, Randy.Dunlap wrote:
> Here's an update (as pointed out off-list).
> Please replace the first one if that works for you.
>
>
> arlan: Fix gcc warning.
>
> With CONFIG_PROC_FS=n, gcc complains:
> drivers/net/wireless/arlan-main.c:1858: warning: statement with no effect
>
> Also remove a useless semi-colon on a #define.
>
> Signed-off-by: Randy Dunlap <rddunlap@osdl.org>
>
> diffstat:=
> drivers/net/wireless/arlan.h | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
I've never touched that driver, but it looks ok to me. I hope
Jeff will pick it up.
Jean
prev parent reply other threads:[~2005-01-27 16:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-26 6:20 [PATCH] arlan: remove gcc warning with CONFIG_PROC_FS=n Randy.Dunlap
2005-01-27 1:38 ` [PATCH] (v2) " Randy.Dunlap
2005-01-27 16:47 ` Jean Tourrilhes [this message]
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=20050127164705.GC747@bougret.hpl.hp.com \
--to=jt@hpl.hp.com \
--cc=jgarzik@pobox.com \
--cc=netdev@oss.sgi.com \
--cc=rddunlap@osdl.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).