From: Felipe Balbi <me@felipebalbi.com>
To: balajitk@ti.com
Cc: linux-kernel@vger.kernel.org, tony@atomide.com,
khilman@deeprootsystems.com, david-b@pacbell.net,
linux-omap@vger.kernel.org, linux-i2c@vger.kernel.org,
sameo@openedhand.com, wim@iguana.be, timo.t.kokkonen@nokia.com,
ben-linux@fluff.org, lrg@slimlogic.co.uk,
broonie@opensource.wolfsonmicro.com,
Santosh Shilimkar <santosh.shilimkar@ti.com>
Subject: Re: [RFC][PATCH 2/4] OMAP4: PMIC: Add support for twl6030 RTC
Date: Mon, 20 Jul 2009 22:08:53 +0300 [thread overview]
Message-ID: <20090720190852.GF7984@gandalf> (raw)
In-Reply-To: <1248097007-14699-1-git-send-email-balajitk@ti.com>
hi,
On Mon, Jul 20, 2009 at 07:06:47PM +0530, balajitk@ti.com wrote:
> @@ -257,15 +257,15 @@ config RTC_DRV_TWL92330
> platforms. The support is integrated with the rest of
> the Menelaus driver; it's not separate module.
>
> -config RTC_DRV_TWL4030
> - tristate "TI TWL4030/TWL5030/TPS659x0"
> - depends on RTC_CLASS && TWL4030_CORE
> +config RTC_DRV_TWL
> + tristate "TI TWL4030/TWL5030/TWL6030/TPS659x0"
> + depends on RTC_CLASS && (TWL4030_CORE || TWL6030_CORE)
> help
> If you say yes here you get support for the RTC on the
> TWL4030 family chips, used mostly with OMAP3 platforms.
>
> This driver can also be built as a module. If so, the module
> - will be called rtc-twl4030.
> + will be called twl-rtc.
no renaming and still wrong, the driver will be called rtc-twl, not
twl-rtc.
anyways, keep the old name
--
balbi
prev parent reply other threads:[~2009-07-20 19:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-20 13:36 [RFC][PATCH 2/4] OMAP4: PMIC: Add support for twl6030 RTC balajitk
2009-07-20 19:08 ` Felipe Balbi [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=20090720190852.GF7984@gandalf \
--to=me@felipebalbi.com \
--cc=balajitk@ti.com \
--cc=ben-linux@fluff.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=david-b@pacbell.net \
--cc=khilman@deeprootsystems.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=sameo@openedhand.com \
--cc=santosh.shilimkar@ti.com \
--cc=timo.t.kokkonen@nokia.com \
--cc=tony@atomide.com \
--cc=wim@iguana.be \
/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).