From: "H. Peter Anvin" <hpa@zytor.com>
To: Peter Hagervall <hager@cs.umu.se>
Cc: junkio@cox.net, git@vger.kernel.org
Subject: Re: [PATCH] Sparse fixes for http-fetch
Date: Thu, 13 Oct 2005 10:51:29 -0700 [thread overview]
Message-ID: <434E9EA1.3030002@zytor.com> (raw)
In-Reply-To: <20051013174203.GA6860@peppar.cs.umu.se>
Peter Hagervall wrote:
> This patch cleans out all sparse warnings from http-fetch.c
>
> I'm a bit uncomfortable with adding extra #ifdefs to avoid either
> 'mixing declaration with code' or 'unused variable' warnings, but I
> figured that since those functions are already littered with #ifdefs I
> might just get away with it. Comments?
>
For the first, you can use extra brackets to create blocks in which
declarations can happen; for the latter, you can (void)var; to specify
that a certain variable may be legitimately unused under some circumstances.
-hpa
next prev parent reply other threads:[~2005-10-13 17:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-13 17:42 [PATCH] Sparse fixes for http-fetch Peter Hagervall
2005-10-13 17:51 ` H. Peter Anvin [this message]
2005-10-13 18:16 ` Junio C Hamano
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=434E9EA1.3030002@zytor.com \
--to=hpa@zytor.com \
--cc=git@vger.kernel.org \
--cc=hager@cs.umu.se \
--cc=junkio@cox.net \
/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.