From: dedekind1@gmail.com (Artem Bityutskiy)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH resend] i.MX53 Nand support
Date: Thu, 30 Aug 2012 09:29:05 +0300 [thread overview]
Message-ID: <1346308145.2848.529.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <1346226019-23560-1-git-send-email-s.hauer@pengutronix.de>
On Wed, 2012-08-29 at 09:40 +0200, Sascha Hauer wrote:
> Hi All,
>
> The following patches add i.MX53 and dt support to mxc_nand. This
> is only a resent based on v3.6-rc3 as it seems this series slipped
> through the cracks last time I posted it.
>
> So Artem, if there are no objections, please consider applying up to
> 3/4, I would then take 4/4 through my tree.
Please, take a look at the l2-mtd.git tree, I already have all these
patches. Actually, they are already in dwmw2's tree, the and were
supposed to be merged already, but unfortunately the merge window was
missed because (a) dwmw2 did not send a pull request early enough and
(b) Linus decided to punish late pull-request senders and closed the
merge window 2 days earlier than usually.
--
Best Regards,
Artem Bityutskiy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120830/63b16be4/attachment.sig>
next prev parent reply other threads:[~2012-08-30 6:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-29 7:40 [PATCH resend] i.MX53 Nand support Sascha Hauer
2012-08-29 7:40 ` [PATCH 1/4] mtd nand mxc_nand: Use managed resources Sascha Hauer
2012-08-29 7:40 ` [PATCH 2/4] mtd nand mxc_nand: swap iomem resource order Sascha Hauer
2012-08-29 7:40 ` [PATCH 3/4] mtd nand mxc_nand: add i.MX53 support Sascha Hauer
2012-08-29 7:40 ` [PATCH 4/4] ARM i.MX5: Add nand oftree support Sascha Hauer
2012-08-30 6:29 ` Artem Bityutskiy [this message]
2012-08-30 6:31 ` [PATCH resend] i.MX53 Nand support 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=1346308145.2848.529.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.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).