From: Artem Bityutskiy <dedekind1@gmail.com>
To: MTD Maling List <linux-mtd@lists.infradead.org>
Subject: [PATCH 0/9] mtd: MTD API rework
Date: Wed, 8 Feb 2012 17:21:16 +0200 [thread overview]
Message-ID: <1328714485-19536-1-git-send-email-dedekind1@gmail.com> (raw)
From: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
Hi,
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.
Please, do test the changes if you use MTD - it is easy to break something when
you are trying to clean-up ancient crap.
Artem.
next reply other threads:[~2012-02-08 15:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 15:21 Artem Bityutskiy [this message]
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 ` [PATCH 0/9] mtd: MTD API rework Artem Bityutskiy
2012-03-19 21:25 ` 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=1328714485-19536-1-git-send-email-dedekind1@gmail.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