From: Adrian Hunter <adrian.hunter@nokia.com>
To: Kevin Cernekee <kpc.mtd@gmail.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH 1/2] [MTD] CORE: New ioctl calls for >4GiB device support (take 2)
Date: Fri, 20 Mar 2009 10:11:10 +0200 [thread overview]
Message-ID: <49C34F9E.2090701@nokia.com> (raw)
In-Reply-To: <a95a62fe0903192237u64b67efdubd328c8f0cd61b49@mail.gmail.com>
Kevin Cernekee wrote:
> Extend the MTD user ABI to access >4GiB devices using 64-bit offsets.
> Add compat_ioctl support to the MTD ABI.
>
> New ioctls: MEMABIINFO MEMGETINFO64 MEMERASE64 MEMWRITEOOB64 MEMREADOOB64
> MEMLOCK64 MEMUNLOCK64 MEMGETREGIONINFO64
>
> Signed-off-by: Kevin Cernekee <kpc.mtd@gmail.com>
> ---
> drivers/mtd/compat_ioctl.c | 233 +++++++++++++
> drivers/mtd/compat_ioctl.h | 89 +++++
> drivers/mtd/mtdchar.c | 817 ++++++++++++++++++++++++++++---------------
> include/mtd/mtd-abi.h | 69 ++++-
> include/mtd/mtd-user.h | 4 +
> 5 files changed, 921 insertions(+), 291 deletions(-)
> create mode 100644 drivers/mtd/compat_ioctl.c
> create mode 100644 drivers/mtd/compat_ioctl.h
>
> diff --git a/drivers/mtd/compat_ioctl.c b/drivers/mtd/compat_ioctl.c
> new file mode 100644
> index 0000000..ee98f71
> --- /dev/null
> +++ b/drivers/mtd/compat_ioctl.c
> @@ -0,0 +1,233 @@
> +/*
> + * MTD compat_ioctl implementation
That is not how it is done. See fs/compat_ioctl.c
<snip>
>
> +struct mtd_abi_info {
> + uint32_t major;
> + uint32_t minor;
> + uint32_t patchlevel;
> + uint32_t res0[8];
> +};
> +
ioctl versioning is unlikely to be accepted by the wider community.
Try posting to LKML for more feedback on that.
prev parent reply other threads:[~2009-03-20 8:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-20 5:37 [PATCH 1/2] [MTD] CORE: New ioctl calls for >4GiB device support (take 2) Kevin Cernekee
2009-03-20 8:11 ` Adrian Hunter [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=49C34F9E.2090701@nokia.com \
--to=adrian.hunter@nokia.com \
--cc=kpc.mtd@gmail.com \
--cc=linux-mtd@lists.infradead.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.