public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: John Calixto <john.calixto@modsystems.com>
To: linux-mmc@vger.kernel.org
Cc: "Michał Mirosław" <mirqus@gmail.com>,
	"Andrei Warkentin" <andreiw@motorola.com>,
	"Arnd Bergmann" <arnd@arndb.de>, "Chris Ball" <cjb@laptop.org>
Subject: v5 changelog - mmc: Add ioctl to let userspace apps send ACMDs
Date: Tue, 12 Apr 2011 15:52:54 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.00.1104121544380.8483@peruna> (raw)

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1021 bytes --]

A small fix for a compiler warning.  Thanks to Michał Mirosław for
suggesting the solution!

Patch history below:

- v5
    - fix 32-bit compiler warning about the 32+64 compat pointer

- v4
    - replace postsleep udelay() with usleep_range()
    - add cmd_timeout_ms field for R1B commands

- v3
    - copy data from userspace before claiming host
    - break out copy from userspace into its own function
    - verify that caller has CAP_SYS_RAWIO
    - rename ``struct sd_ioc_cmd`` to ``struct mmc_ioc_cmd`` because it
      applies generally, not just to SD
    - make struct mmc_ioc_cmd the same between 32-bit and 64-bit to
      simplify compat_ioctl()
    - export include/linux/mmc/ioctl.h when you ``make headers_install``

- v2
    - make initialization of struct declarations match kernel style
    - only allow ioctl() on whole block device, not partition
    - remove extraneous printks
    - implement compat_ioctl()
    - remove version field from ``struct sd_ioc_cmd``

John

             reply	other threads:[~2011-04-12 22:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-12 22:52 John Calixto [this message]
2011-04-12 22:57 ` [PATCH v5] mmc: Add ioctl to let userspace apps send ACMDs John Calixto
2011-04-12 23:13   ` John Calixto

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=alpine.DEB.2.00.1104121544380.8483@peruna \
    --to=john.calixto@modsystems.com \
    --cc=andreiw@motorola.com \
    --cc=arnd@arndb.de \
    --cc=cjb@laptop.org \
    --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