From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Harvey Harrison <harvey.harrison@gmail.com>
Cc: David Miller <davem@davemloft.net>,
linux-netdev <netdev@vger.kernel.org>
Subject: Re: ni52.c warnings explosion
Date: Thu, 21 Feb 2008 10:56:16 +0000 [thread overview]
Message-ID: <20080221105616.52c2406f@core> (raw)
In-Reply-To: <1203578784.20345.4.camel@brick>
On Wed, 20 Feb 2008 23:26:24 -0800
Harvey Harrison <harvey.harrison@gmail.com> wrote:
> Dave,
>
> Somewhere between 2.6.25-rc1 and -rc2 something changed that produces a
> few hundred sparse warnings in ni52.c.
I gave it a massive clean up but I've not annotated it
>
> I see Alan touched it last.
>
> drivers/net/ni52.c:219:15: warning: incorrect type in argument 1 (different address spaces)
> drivers/net/ni52.c:219:15: expected void const volatile [noderef] <asn:2>*addr
> drivers/net/ni52.c:219:15: got unsigned char *<noident>
>
> If you want the full log, let me know.
Throw it my way. I'll go through it but its probably mostly about
annotating it now it uses io spaces.
prev parent reply other threads:[~2008-02-21 11:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-21 7:26 ni52.c warnings explosion Harvey Harrison
2008-02-21 10:56 ` Alan Cox [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=20080221105616.52c2406f@core \
--to=alan@lxorguk.ukuu.org.uk \
--cc=davem@davemloft.net \
--cc=harvey.harrison@gmail.com \
--cc=netdev@vger.kernel.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