From: Johannes Berg <johannes@sipsolutions.net>
To: Dave <kilroyd@googlemail.com>
Cc: Pavel Roskin <proski@gnu.org>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 00/05] orinoco: Agere/Lucent firmware download
Date: Fri, 14 Sep 2007 21:06:47 +0200 [thread overview]
Message-ID: <1189796807.3974.53.camel@johannes.berg> (raw)
In-Reply-To: <46EAD760.9020102@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 405 bytes --]
On Fri, 2007-09-14 at 19:48 +0100, Dave wrote:
> Either that was painless, or I did it wrong. Using sparse 3.0 the only
> warnings were in orinoco.c, related to the use of ARRAY_SIZE. Errors
> are false positives.
They're errors tho so sparse aborts and stops parsing the file at that
point. A new git sparse can actually parse ARRAY_SIZE though, I can only
recommend getting that.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2007-09-14 19:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-12 21:09 [PATCH 00/05] orinoco: Agere/Lucent firmware download Dave
2007-09-14 5:05 ` Pavel Roskin
2007-09-14 17:53 ` Dave
2007-09-14 18:48 ` Dave
2007-09-14 19:06 ` Johannes Berg [this message]
2007-09-14 21:01 ` Dave
2007-09-14 21:13 ` Johannes Berg
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=1189796807.3974.53.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=kilroyd@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=proski@gnu.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).