From: Pavel Roskin <proski@gnu.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH] d80211: fix sparse warnings
Date: Tue, 27 Feb 2007 02:16:25 -0500 [thread overview]
Message-ID: <1172560585.19312.20.camel@dv> (raw)
In-Reply-To: <1172539109.5835.28.camel@dv>
On Mon, 2007-02-26 at 20:18 -0500, Pavel Roskin wrote:
> Great catch! I have reduced this to a simple test case where sparse
> behaves unreasonably, and I'm going to send it to sparse developers as a
> bug report.
Linus has replied that it's not a bug:
http://marc.theaimsgroup.com/?l=linux-sparse&m=117254997313979&w=2
He suggests in the end how to avoid that warning.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2007-02-27 7:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-26 22:59 [PATCH] d80211: fix sparse warnings Johannes Berg
2007-02-27 1:18 ` Pavel Roskin
2007-02-27 7:16 ` Pavel Roskin [this message]
2007-02-27 8:28 ` Johannes Berg
2007-02-27 15:40 ` Michael Buesch
2007-02-27 15:45 ` Michael Wu
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=1172560585.19312.20.camel@dv \
--to=proski@gnu.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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