From: Artem Bityutskiy <dedekind1@gmail.com>
To: MTD Maling List <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH 0/9] mtd: MTD API rework
Date: Wed, 08 Feb 2012 18:05:44 +0200 [thread overview]
Message-ID: <1328717144.22240.66.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <1328714485-19536-1-git-send-email-dedekind1@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2013 bytes --]
On Wed, 2012-02-08 at 17:21 +0200, Artem Bityutskiy wrote:
> here are the latest MTD API rework patches. I have plans to also harmonize the
> OOB-related functions, try to harmonize alignment checking in erase and write
> functions as well. Not sure I'll have time for this, though, will see.
I forgot this:
drivers/mtd/chips/cfi_cmdset_0001.c | 26 ++--
drivers/mtd/chips/cfi_cmdset_0002.c | 21 ---
drivers/mtd/chips/cfi_cmdset_0020.c | 15 --
drivers/mtd/chips/cfi_util.c | 6 -
drivers/mtd/chips/map_absent.c | 2 -
drivers/mtd/chips/map_ram.c | 4 -
drivers/mtd/chips/map_rom.c | 3 +-
drivers/mtd/devices/block2mtd.c | 17 ---
drivers/mtd/devices/doc2000.c | 12 --
drivers/mtd/devices/doc2001.c | 9 --
drivers/mtd/devices/doc2001plus.c | 9 --
drivers/mtd/devices/lart.c | 10 --
drivers/mtd/devices/m25p80.c | 31 -----
drivers/mtd/devices/ms02-nv.c | 8 -
drivers/mtd/devices/mtd_dataflash.c | 21 ---
drivers/mtd/devices/mtdram.c | 23 +---
drivers/mtd/devices/phram.c | 33 +-----
drivers/mtd/devices/pmc551.c | 85 ++++++------
drivers/mtd/devices/slram.c | 31 +----
drivers/mtd/devices/spear_smi.c | 28 ----
drivers/mtd/devices/sst25l.c | 20 ---
drivers/mtd/lpddr/lpddr_cmds.c | 21 ++--
drivers/mtd/maps/vmu-flash.c | 8 -
drivers/mtd/mtdconcat.c | 59 +--------
drivers/mtd/mtdcore.c | 254 +++++++++++++++++++++++++++++++++++
drivers/mtd/mtdpart.c | 48 +------
drivers/mtd/nand/nand_base.c | 38 -----
drivers/mtd/onenand/onenand_base.c | 23 ---
drivers/mtd/ubi/gluebi.c | 19 ---
include/linux/mtd/mtd.h | 201 +++++-----------------------
include/linux/mtd/pmc551.h | 78 -----------
31 files changed, 360 insertions(+), 803 deletions(-)
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-02-08 16:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 15:21 [PATCH 0/9] mtd: MTD API rework Artem Bityutskiy
2012-02-08 15:21 ` [PATCH 1/9] mtd: return error code from mtd_unpoint Artem Bityutskiy
2012-02-08 15:21 ` [PATCH 2/9] mtd: add offset and length checks to the API function Artem Bityutskiy
2012-02-08 15:21 ` [PATCH 3/9] mtd: do not duplicate length and offset checks in drivers Artem Bityutskiy
2012-02-08 15:21 ` [PATCH 4/9] mtd: remove R/O checking duplication Artem Bityutskiy
2012-02-08 15:21 ` [PATCH 5/9] mtd: remove retlen zeroing duplication Artem Bityutskiy
2012-02-08 15:21 ` [PATCH 6/9] mtd: remove junk pmc551.h Artem Bityutskiy
2012-02-08 15:21 ` [PATCH 7/9] mtd: harmonize mtd_point interface implementation Artem Bityutskiy
2012-02-08 15:21 ` [PATCH 8/9] mtd: move zero length verification to MTD API functions Artem Bityutskiy
2012-02-08 15:21 ` [PATCH 9/9] mtd: check for zero length in OTP functions Artem Bityutskiy
2012-02-08 16:05 ` Artem Bityutskiy [this message]
2012-03-19 21:25 ` [PATCH 0/9] mtd: MTD API rework Robert Jarzmik
2012-04-02 7:21 ` Artem Bityutskiy
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=1328717144.22240.66.camel@sauron.fi.intel.com \
--to=dedekind1@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox