From: Artem Bityutskiy <dedekind1@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Mike Turquette <mturquette@linaro.org>,
linux-mtd@lists.infradead.org, Mike Turquette <mturquette@ti.com>,
David Woodhouse <dwmw2@infradead.org>,
linux-arm-kernel@lists.infradead.org,
Alessandro Rubini <rubini@unipv.it>
Subject: Re: [PATCH 1/2] ARM: nomadik: switch over to using the FSMC driver
Date: Thu, 11 Oct 2012 14:07:12 +0300 [thread overview]
Message-ID: <1349953632.12014.8.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <1349335709-13399-1-git-send-email-linus.walleij@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 514 bytes --]
On Thu, 2012-10-04 at 09:28 +0200, Linus Walleij wrote:
> The Nomadik NAND driver is really just a subset of the existing
> FSMC driver, so let's switch over to using that driver instead,
> since it handles more variants of this chip. The callbacks for
> setting up the chip is doing stuff now handled by the FSMC
> driver.
>
> Cc: Alessandro Rubini <rubini@unipv.it>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Pushed both to l2-mtd.git, thanks!
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: dedekind1@gmail.com (Artem Bityutskiy)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: nomadik: switch over to using the FSMC driver
Date: Thu, 11 Oct 2012 14:07:12 +0300 [thread overview]
Message-ID: <1349953632.12014.8.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <1349335709-13399-1-git-send-email-linus.walleij@linaro.org>
On Thu, 2012-10-04 at 09:28 +0200, Linus Walleij wrote:
> The Nomadik NAND driver is really just a subset of the existing
> FSMC driver, so let's switch over to using that driver instead,
> since it handles more variants of this chip. The callbacks for
> setting up the chip is doing stuff now handled by the FSMC
> driver.
>
> Cc: Alessandro Rubini <rubini@unipv.it>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Pushed both to l2-mtd.git, thanks!
--
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/20121011/fdb275c4/attachment-0001.sig>
next prev parent reply other threads:[~2012-10-11 11:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-04 7:28 [PATCH 1/2] ARM: nomadik: switch over to using the FSMC driver Linus Walleij
2012-10-04 7:28 ` Linus Walleij
2012-10-05 12:52 ` Linus Walleij
2012-10-05 12:52 ` Linus Walleij
2012-10-05 12:58 ` Alessandro Rubini
2012-10-05 12:58 ` Alessandro Rubini
2012-10-11 23:49 ` Mike Turquette
2012-10-11 23:49 ` Mike Turquette
2012-10-11 11:07 ` Artem Bityutskiy [this message]
2012-10-11 11:07 ` Artem Bityutskiy
2012-10-11 18:04 ` Jean-Christophe PLAGNIOL-VILLARD
2012-10-11 18:04 ` Jean-Christophe PLAGNIOL-VILLARD
2012-10-11 22:20 ` Linus Walleij
2012-10-11 22:20 ` Linus Walleij
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=1349953632.12014.8.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mturquette@linaro.org \
--cc=mturquette@ti.com \
--cc=rubini@unipv.it \
/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.