From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] sh: fix readsl/writesl argument
Date: Tue, 26 Feb 2008 05:23:07 +0000 [thread overview]
Message-ID: <20080226052307.GF19814@linux-sh.org> (raw)
In-Reply-To: <20080220102853.22714.57848.sendpatchset@clockwork.opensource.se>
On Thu, Feb 21, 2008 at 11:57:12AM +0900, Magnus Damm wrote:
> Hi Stuart,
>
> On Wed, Feb 20, 2008 at 9:15 PM, Stuart MENEFY <stuart.menefy@st.com> wrote:
> > Magnus Damm wrote:
> > > writesl() and readsl() use void __iomem * as argument but the current sh
> > > version of __raw_writesl()/__rawreadsl() takes unsigned long. Casting the
> > > pointer fixes smc91x warnings.
> > ...
> >
> > > --- 0001/include/asm-sh/io.h
> > > +++ work/include/asm-sh/io.h 2008-02-20 16:34:28.000000000 +0900
> >
> > > -#define writesl __raw_writesl
> > > -#define readsl __raw_readsl
> > > +#define writesl(m, a, c) __raw_writesl((unsigned long)(m), (a), (c))
> > > +#define readsl(m, a, c) __raw_readsl((unsigned long)(m), (a), (c))
> >
> > Wouldn't it be better to do this as inline functions, that way we don't
> > loose the type checking?
>
> Yes, I think so too. But step by step. =) I'm planning on replacing a
> lot of code in io.h actually, and I'll use inlines and avoid casting
> to get proper type checking then. Thanks!
>
There's not a lot of point in merging this for 2.6.25, so lets just drop
this and focus on the proper cleanup for the 2.6.26 window instead.
next prev parent reply other threads:[~2008-02-26 5:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-20 10:28 [PATCH] sh: fix readsl/writesl argument Magnus Damm
2008-02-20 12:15 ` Stuart MENEFY
2008-02-21 2:57 ` Magnus Damm
2008-02-26 5:23 ` Paul Mundt [this message]
2008-02-26 6:39 ` Magnus Damm
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=20080226052307.GF19814@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@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 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.