From: dedekind1@gmail.com (Artem Bityutskiy)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] MTD: NAND: ams-delta: convert to platform driver
Date: Wed, 15 Dec 2010 11:37:45 +0200 [thread overview]
Message-ID: <1292405865.2512.28.camel@localhost> (raw)
In-Reply-To: <201012142109.42784.jkrzyszt@tis.icnet.pl>
On Tue, 2010-12-14 at 21:09 +0100, Janusz Krzysztofik wrote:
> In its current form, the driver may interfere with different hardware on
> different boards if built into the kernel, hence is not suitable for
> inclusion into a defconfig, inteded to be usable with multiple OMAP1 cpu and
> machine types.
>
> Convert it to a platform driver, that should be free from this issue.
>
> Created and tested against linux-2.6.37-rc5 on Amstrad Delta.
>
> Signed-off-by: Janusz Krzysztofik <jkrzyszt@tis.icnet.pl>
Pushed to l2-mtd-2.6.git, thanks!
--
Best Regards,
Artem Bityutskiy (????? ????????)
prev parent reply other threads:[~2010-12-15 9:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-11 17:40 [PATCH] MTD: NAND: ams-delta: convert to platform driver Janusz Krzysztofik
2010-12-14 17:00 ` Artem Bityutskiy
2010-12-14 20:09 ` [PATCH v2] " Janusz Krzysztofik
2010-12-14 22:28 ` Tony Lindgren
2010-12-15 9:37 ` Artem Bityutskiy [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=1292405865.2512.28.camel@localhost \
--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).