From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] ARM: mach-shmobile: driver kconfig update
Date: Wed, 10 Feb 2010 03:50:15 +0000 [thread overview]
Message-ID: <20100210035015.GB21624@linux-sh.org> (raw)
In-Reply-To: <20100209095621.1458.15191.sendpatchset@rxone.opensource.se>
On Tue, Feb 09, 2010 at 06:56:21PM +0900, Magnus Damm wrote:
> This patch updates the Kconfig entries for various
> SuperH drivers to enable use on SH-Mobile G-series.
>
Why? If you have a user for one of these, then send the Kconfig-enabling
part along with that patch, otherwise this is just introducing merge
conflicts for no reason whatsoever.
> While at it, add a HAVE_CLK dependency for drivers
> that use the clock framework.
>
HAVE_CLK is really only useful for drivers that are generically exposed.
For ones that are restricted to SUPERH || ARCH_SHMOBILE it doesn't really
make any sense, since the clock framework will always be there anyways.
prev parent reply other threads:[~2010-02-10 3:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-09 9:56 [PATCH] ARM: mach-shmobile: driver kconfig update Magnus Damm
2010-02-10 3:50 ` Paul Mundt [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=20100210035015.GB21624@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@vger.kernel.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).