From: Arnd Bergmann <arnd@arndb.de>
To: John Calixto <john.calixto@modsystems.com>
Cc: "Michał Mirosław" <mirqus@gmail.com>,
linux-mmc@vger.kernel.org,
"Andrei Warkentin" <andreiw@motorola.com>,
"Chris Ball" <cjb@laptop.org>
Subject: Re: [PATCH v6] mmc: Add mmc CMD+ACMD passthrough ioctl
Date: Wed, 20 Apr 2011 21:38:53 +0200 [thread overview]
Message-ID: <201104202138.53981.arnd@arndb.de> (raw)
In-Reply-To: <alpine.DEB.2.00.1104201226510.28361@peruna>
On Wednesday 20 April 2011 21:34:20 John Calixto wrote:
> On Wed, 20 Apr 2011, Arnd Bergmann wrote:
> >
> > No need for a union or a ptr_size member in the struct. Just use
> > a single __u64 and let the user cast the pointer to that. This
> > will work on all architectures.
> >
> > > However, I still think it should be implemented in compat_ioctl()
> > > because compat_blkdev_ioctl() expects it. Either that, or I add to the
> > > big switch in compat_blkdev_driver_ioctl(), and spreading this change
> > > out to block/compat_ioctl.c does not seem like The Right Thing to me.
> >
>
> In the non-compat use case with a 32-bit kernel + 32-bit userspace (e.g.
> ARM), the casting of the __u64 to a pointer causes a compiler warning.
> It works as intended, so it's not an error, but it does not feel right
> to just silence the compiler. That's why I used a memcpy with with
> explicit pointer size directly in the struct. How else would you
> recommend I handle this?
Just cast to unsigned long and then to pointer.
Arnd
next prev parent reply other threads:[~2011-04-20 19:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-14 0:34 v6 changelog for mmc ioctl patch John Calixto
2011-04-14 0:38 ` [PATCH v6] mmc: Add mmc CMD+ACMD passthrough ioctl John Calixto
2011-04-20 17:12 ` John Calixto
2011-04-20 17:29 ` Chris Ball
2011-04-21 10:47 ` Arnd Bergmann
2011-04-20 17:31 ` Michał Mirosław
2011-04-20 17:38 ` John Calixto
2011-04-20 18:06 ` Michał Mirosław
2011-04-20 18:23 ` Michał Mirosław
2011-04-20 19:06 ` John Calixto
2011-04-20 19:17 ` Arnd Bergmann
2011-04-20 19:34 ` John Calixto
2011-04-20 19:38 ` Arnd Bergmann [this message]
2011-04-20 19:46 ` Michał Mirosław
2011-04-20 20:47 ` John Calixto
2011-04-20 22:28 ` Chris Ball
2011-04-21 5:11 ` Arnd Bergmann
2011-04-21 10:28 ` Michał Mirosław
2011-04-21 11:15 ` Arnd Bergmann
2011-04-21 11:47 ` Michał Mirosław
2011-04-21 12:39 ` Arnd Bergmann
2011-04-21 13:40 ` Michał Mirosław
2011-04-20 22:13 ` Chris Ball
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=201104202138.53981.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=andreiw@motorola.com \
--cc=cjb@laptop.org \
--cc=john.calixto@modsystems.com \
--cc=linux-mmc@vger.kernel.org \
--cc=mirqus@gmail.com \
/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