From: Tony Lindgren <tony@atomide.com>
To: Dirk Behme <dirk.behme@googlemail.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
Steve Sakoman <sakoman@gmail.com>
Subject: Re: [PATCH 0/3 v2] OMAP3 Beagle: Enable nand support
Date: Tue, 5 Aug 2008 12:09:22 +0300 [thread overview]
Message-ID: <20080805090921.GH7193@atomide.com> (raw)
In-Reply-To: <48972701.2080006@googlemail.com>
* Dirk Behme <dirk.behme@googlemail.com> [080804 19:01]:
> This series of patches adds NAND support to the BeagleBoard.
>
> The first patch in the series builds on work by Teerth Reddy
> <teerth@ti.com> and Steve Sakoman <sakoman@gmail.com> to extend the
> omap2 nand driver to work with both omap2 and omap3 architectures (as
> well as adding/clarifying comments).
>
> The second patch adds the beagle nand support, and the final patch
> enables the nand driver and jffs2 support in the beagle defconfig.
>
> The patch set was reviewed by Khasim Syed Mohammed <khasim@ti.com> prior
> to this submission. It was tested on Rev A and B BeagleBoards.
>
> This v2 replaces http://marc.info/?l=linux-omap&m=121230229625544&w=2
>
> Changes in v2:
>
> - Apply cleanly to recent git (defconfig, drivers/mtd/nand/omap2.c)
> - Beagle has only NAND. This results in small config. Move configuration
> to board-omap3beagle.c and don't create a new file
> board-omap3beagle-flash.c for it.
Pushing this series today.
Tony
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2008-08-05 9:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-04 15:57 [PATCH 0/3 v2] OMAP3 Beagle: Enable nand support Dirk Behme
2008-08-05 9:09 ` Tony Lindgren [this message]
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=20080805090921.GH7193@atomide.com \
--to=tony@atomide.com \
--cc=dirk.behme@googlemail.com \
--cc=linux-omap@vger.kernel.org \
--cc=sakoman@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.