From: Ricky lloyd <ricky.lloyd@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: 2.6.9-rc4: warnings galore
Date: Mon, 11 Oct 2004 14:32:53 +0530 [thread overview]
Message-ID: <1a50bd37041011020211e96208@mail.gmail.com> (raw)
hi,
Now that readw(), writew() etc family of routines are inline
functions, looks like this change
has resulted in gcc spewing out lots of warnings about not type
casting the args for these
routines.
is typecasting all the concerned args to (void __iomem *) the only
solution to this ? if yes,
there are a lot of places to fix this in the drivers/ subdir. I can go
ahead and submit a patch.
did i miss anything by the way ???
--
-> Ricky
reply other threads:[~2004-10-11 9:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1a50bd37041011020211e96208@mail.gmail.com \
--to=ricky.lloyd@gmail.com \
--cc=linux-kernel@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