From: Ralf Baechle <ralf@linux-mips.org>
To: Florian Fainelli <florian@openwrt.org>
Cc: linux-mips@linux-mips.org, David Daney <ddaney@caviumnetworks.com>
Subject: Re: [PATCH 2/2] octeon: only build flash_setup code when CONFIG_MTD is set
Date: Mon, 22 Jun 2009 15:40:42 +0100 [thread overview]
Message-ID: <20090622144042.GC25289@linux-mips.org> (raw)
In-Reply-To: <200906221116.21621.florian@openwrt.org>
On Mon, Jun 22, 2009 at 11:16:21AM +0200, Florian Fainelli wrote:
> This patch makes the flash_setup code be compiled only when
> CONFIG_MTD is set, it does make sense to register a physmap
> platform driver without the MTD subsystem being enabled.
No. A user might build the MTD subsystem as a module and then insert it
into a running system so the idea is to always register the devices. This
also keeps the information in /proc/iomem rsp. /proc/iostat and sysfs
more useful.
Ralf
next prev parent reply other threads:[~2009-06-22 14:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-22 9:16 [PATCH 2/2] octeon: only build flash_setup code when CONFIG_MTD is set Florian Fainelli
2009-06-22 14:40 ` Ralf Baechle [this message]
2009-06-22 21:05 ` Florian Fainelli
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=20090622144042.GC25289@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=ddaney@caviumnetworks.com \
--cc=florian@openwrt.org \
--cc=linux-mips@linux-mips.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).