From: Dave <kilroyd@googlemail.com>
To: Johannes Berg <johannes@sipsolutions.net>
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 22:01:12 +0100 [thread overview]
Message-ID: <46EAF698.8030604@gmail.com> (raw)
In-Reply-To: <1189796807.3974.53.camel@johannes.berg>
Johannes Berg wrote:
> 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.
Repeated with latest sparse from git. No warnings.
<snip>
CHECK /usr/src/linux-current/linux-2.6/drivers/net/irda/sir_dongle.c
CHECK /usr/src/linux-current/linux-2.6/drivers/net/wireless/orinoco.c
CHECK /usr/src/linux-current/linux-2.6/drivers/net/wireless/hermes.c
CHECK /usr/src/linux-current/linux-2.6/drivers/net/wireless/hermes_dld.c
CHECK /usr/src/linux-current/linux-2.6/drivers/net/wireless/orinoco_cs.c
CHECK /usr/src/linux-current/linux-2.6/drivers/net/wireless/orinoco_plx.c
CHECK /usr/src/linux-current/linux-2.6/drivers/net/wireless/orinoco_pci.c
CHECK /usr/src/linux-current/linux-2.6/drivers/net/wireless/orinoco_tmd.c
CHECK /usr/src/linux-current/linux-2.6/drivers/net/wireless/orinoco_nortel.c
CHECK /usr/src/linux-current/linux-2.6/drivers/net/wireless/spectrum_cs.c
CHECK /usr/src/linux-current/linux-2.6/drivers/net/wireless/zd1201.c
<snip>
Regards,
Dave.
next prev parent reply other threads:[~2007-09-14 21:01 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
2007-09-14 21:01 ` Dave [this message]
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=46EAF698.8030604@gmail.com \
--to=kilroyd@googlemail.com \
--cc=johannes@sipsolutions.net \
--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 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.