From: Sam Ravnborg <sam@ravnborg.org>
To: linux-os@analogic.com
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
linux-net@vger.kernel.org
Subject: Re: [PATCH 167] Kill unused variables in the net code
Date: Fri, 7 Jan 2005 23:56:31 +0100 [thread overview]
Message-ID: <20050107225631.GA21884@mars.ravnborg.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0501071636160.21727@chaos.analogic.com>
On Fri, Jan 07, 2005 at 04:38:36PM -0500, linux-os wrote:
> >-#define read_unlock(lock) do { } while(0)
> >+#define read_unlock(lock) (void)(lock) /* Not "unused variable". */
>
> But don't all you need to do is:
>
> #define read_unlock(x)
Then tbl will still be unused - and compiler will emit warning.
Sam
prev parent reply other threads:[~2005-01-07 22:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-07 21:11 Geert Uytterhoeven
2005-01-07 21:38 ` linux-os
2005-01-07 22:20 ` Geert Uytterhoeven
2005-01-07 22:56 ` Sam Ravnborg [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=20050107225631.GA21884@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=linux-os@analogic.com \
--cc=marcelo.tosatti@cyclades.com \
/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
all inboxes | Powered by JetHome®