From: Marc Kleine-Budde <mkl@pengutronix.de>
To: barebox@lists.infradead.org
Cc: sha@pengutronix.de
Subject: [PATCH V2 0/3] at91 fixes
Date: Tue, 22 Feb 2011 12:32:43 +0100 [thread overview]
Message-ID: <1298374366-6956-1-git-send-email-mkl@pengutronix.de> (raw)
Hello,
this patch series fixes some problems on the at91sam9g45 and adds support for
flash based bad block table to the atmel nand driver.
changes since V1:
- fix wording in commit message
The following changes since commit 58ec1a81a16a758bc6125f7736d13137c5b7e17f:
Merge branch 'tx25' into next (2011-02-18 11:11:48 +0100)
are available in the git repository at:
git://git.pengutronix.de/git/mkl/barebox.git at91
Juergen Beisert (1):
at91sam9g45_devices: fix compilation if NAND driver is enabled
Marc Kleine-Budde (2):
at91sam9g45_devices: don't hardcode nand ecc mode
atmel_nand: add support for flash based bad block table
arch/arm/mach-at91/at91sam9g45_devices.c | 2 +-
arch/arm/mach-at91/include/mach/board.h | 1 +
drivers/mtd/nand/atmel_nand.c | 5 +++++
3 files changed, 7 insertions(+), 1 deletions(-)
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2011-02-22 11:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-22 11:32 Marc Kleine-Budde [this message]
2011-02-22 11:32 ` [PATCH V2 1/3] at91sam9g45_devices: fix compilation if NAND driver is enabled Marc Kleine-Budde
2011-02-22 11:32 ` [PATCH V2 2/3] at91sam9g45_devices: don't hardcode nand ecc mode Marc Kleine-Budde
2011-02-22 12:02 ` Jean-Christophe PLAGNIOL-VILLARD
2011-02-22 11:32 ` [PATCH V2 3/3] atmel_nand: add support for flash based bad block table Marc Kleine-Budde
2011-02-22 12:03 ` Jean-Christophe PLAGNIOL-VILLARD
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=1298374366-6956-1-git-send-email-mkl@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=sha@pengutronix.de \
/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