From: rubini-list@gnudd.com (Alessandro Rubini)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] Allow Nand and OneNand to coexist
Date: Sun, 20 Sep 2009 23:18:27 +0200 [thread overview]
Message-ID: <cover.1253480933.git.rubini@unipv.it> (raw)
In-Reply-To: 20090920170130.GA19668@mail.gnudd.com
These three patches are a possible solution to the problem I had with
Nand and OneNand in the nhk-8815.c source file, as described in my
previous RFC post.
The first patch fixes code duplication between nand.h and
bbm.h. Actually, it replicates a fix I made to U-Boot some months ago
for the same reason. Without it, we have the same structure (with the
same name) declared in two different headers.
The second patch unifies nand_state_t and onenand_state_t into
flstate_t. Most states were exactly the same, and no user of those
types is affected by having more states than needed. This avoid
redefinition errors for FL_READY and similar values. I chose to
keep flstate_t (the NOR one), as it's name is the most generic.
The third, trivial patch, enables OneNand for Nomadik, including both
<linux/mtd/nand.h> and <linux/mtd/onenand.h>, since it's now possible
to do it.
Alessandro Rubini (3):
mtd: use bbm.h in nand.h
mtd: unify status enum from three headers
ARM Nomadik: use new OneNand name and pdata
arch/arm/mach-nomadik/board-nhk8815.c | 11 ++--
include/linux/mtd/bbm.h | 35 ++++++------
include/linux/mtd/flashchip.h | 7 +++
include/linux/mtd/nand.h | 93 +-------------------------------
include/linux/mtd/onenand.h | 19 +------
5 files changed, 36 insertions(+), 129 deletions(-)
next parent reply other threads:[~2009-09-20 21:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090920170130.GA19668@mail.gnudd.com>
2009-09-20 21:18 ` Alessandro Rubini [this message]
2009-09-20 21:27 ` [PATCH 0/3] Allow Nand and OneNand to coexist Alessandro Rubini
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=cover.1253480933.git.rubini@unipv.it \
--to=rubini-list@gnudd.com \
--cc=linux-arm-kernel@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;
as well as URLs for NNTP newsgroup(s).