mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org
Subject: nand patches
Date: Mon, 11 Apr 2011 16:11:47 +0200	[thread overview]
Message-ID: <1302531111-29244-1-git-send-email-s.hauer@pengutronix.de> (raw)

Some more nand cleanup. The badblock device code is moved from
the nand command to drivers/mtd to make it work without the command.

Sascha Hauer (4):
      nand: nand_block_markbad is only used with nand write support
      nand: move bb handling code to drivers/mtd/nand
      nand bb: switch to cdev operations
      nand bb: add proper bb remove function

 commands/nand.c              |  263 +-------------------------------------
 drivers/mtd/nand/Makefile    |    2 +-
 drivers/mtd/nand/nand-bb.c   |  291 ++++++++++++++++++++++++++++++++++++++++++
 drivers/mtd/nand/nand.c      |    2 +
 drivers/mtd/nand/nand.h      |    1 +
 drivers/mtd/nand/nand_base.c |   23 +---
 include/nand.h               |    5 +
 7 files changed, 304 insertions(+), 283 deletions(-)
 create mode 100644 drivers/mtd/nand/nand-bb.c

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2011-04-11 14:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-11 14:11 Sascha Hauer [this message]
2011-04-11 14:11 ` [PATCH 1/4] nand: nand_block_markbad is only used with nand write support Sascha Hauer
2011-04-11 14:11 ` [PATCH 2/4] nand: move bb handling code to drivers/mtd/nand Sascha Hauer
2011-04-11 14:11 ` [PATCH 3/4] nand bb: switch to cdev operations Sascha Hauer
2011-04-11 14:11 ` [PATCH 4/4] nand bb: add proper bb remove function Sascha Hauer

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=1302531111-29244-1-git-send-email-s.hauer@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@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