From: dedekind1@gmail.com (Artem Bityutskiy)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5] MTD: LPC32xx SLC NAND driver
Date: Wed, 06 Jun 2012 11:42:48 +0300 [thread overview]
Message-ID: <1338972168.6875.7.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <1338837901-24075-1-git-send-email-stigge@antcom.de>
On Mon, 2012-06-04 at 21:25 +0200, Roland Stigge wrote:
> +config MTD_NAND_SLC_LPC32XX
> + bool "NXP LPC32xx SLC Controller"
Why bool and not tristate here? Why you force this to be compiled-in and
make it impossible to be a kernel module like other drivers are?
--
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/20120606/b4a9e1ee/attachment.sig>
next prev parent reply other threads:[~2012-06-06 8:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-04 19:25 [PATCH v5] MTD: LPC32xx SLC NAND driver Roland Stigge
2012-06-04 19:25 ` [PATCH v4] MTD: LPC32xx MLC " Roland Stigge
2012-06-06 8:42 ` Artem Bityutskiy [this message]
2012-06-06 9:01 ` [PATCH v5] MTD: LPC32xx SLC " Roland Stigge
2012-06-06 8:48 ` Artem Bityutskiy
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=1338972168.6875.7.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).