public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alessandro Zummo <a.zummo@towertech.it>
To: linux-kernel@vger.kernel.org
Cc: akpm@zip.com.au, akpm@osdl.org,
	Yoichi Yuasa <yoichi_yuasa@tripeaks.co.jp>
Subject: [PATCH 10/10] RTC subsystem, VR41XX cleanup
Date: Fri, 31 Mar 2006 12:04:33 +0200	[thread overview]
Message-ID: <20060331100425.001583000@towertech.it> (raw)
In-Reply-To: 20060331100423.175139000@towertech.it

[-- Attachment #1: rtc-subsys-drv-vr41xx-kconfig.patch --]
[-- Type: text/plain, Size: 852 bytes --]

 Cleaned up kconfig entry for the rtc-vr41xx.

Signed-off-by: Alessandro Zummo <a.zummo@towertech.it>
CC: Yoichi Yuasa <yoichi_yuasa@tripeaks.co.jp>
---
 drivers/rtc/Kconfig |    8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

--- linux-rtc.orig/drivers/rtc/Kconfig	2006-03-31 11:39:15.000000000 +0200
+++ linux-rtc/drivers/rtc/Kconfig	2006-03-31 11:49:09.000000000 +0200
@@ -148,8 +148,14 @@ config RTC_DRV_SA1100
 	  module will be called rtc-sa1100.
 
 config RTC_DRV_VR41XX
-	tristate "NEC VR4100 series RTC"
+	tristate "NEC VR41XX"
 	depends on RTC_CLASS && CPU_VR41XX
+	help
+	  If you say Y here you will get access to the real time clock
+	  built into your NEC VR41XX CPU.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called rtc-vr41xx.
 
 config RTC_DRV_TEST
 	tristate "Test driver/device"

--

  parent reply	other threads:[~2006-03-31 10:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-31 10:04 [PATCH 00/10] RTC subsystem Alessandro Zummo
2006-03-31 10:04 ` [PATCH 01/10] RTC subsystem, DS1672 oscillator handling Alessandro Zummo
2006-03-31 10:04 ` [PATCH 02/10] RTC subsystem, DS1672 cleanup Alessandro Zummo
2006-03-31 10:04 ` [PATCH 03/10] RTC subsystem, X1205 sysfs cleanup Alessandro Zummo
2006-03-31 10:04 ` [PATCH 04/10] RTC subsystem, whitespaces and error messages cleanup Alessandro Zummo
2006-03-31 10:04 ` [PATCH 05/10] RTC subsystem, fix proc output Alessandro Zummo
2006-03-31 10:04 ` [PATCH 06/10] RTC subsystem, RS5C372 sysfs fix Alessandro Zummo
2006-03-31 10:04 ` [PATCH 07/10] RTC subsystem, compact error messages Alessandro Zummo
2006-03-31 10:04 ` [PATCH 08/10] RTC subsystem, SA1100 cleanup Alessandro Zummo
2006-04-02 18:43   ` Pavel Machek
2006-03-31 10:04 ` [PATCH 09/10] RTC subsystem, VR41XX driver Alessandro Zummo
2006-04-01 23:20   ` Andrew Morton
2006-03-31 10:04 ` Alessandro Zummo [this message]
     [not found] ` <Pine.LNX.4.63.0605030826290.1846@pcgl.dsa-ac.de>
     [not found]   ` <20060503105816.65f309f8@inspiron>
     [not found]     ` <Pine.LNX.4.63.0605031120570.1846@pcgl.dsa-ac.de>
     [not found]       ` <20060503121354.61bf3558@inspiron>
     [not found]         ` <Pine.LNX.4.63.0605031223350.1846@pcgl.dsa-ac.de>
     [not found]           ` <20060503122555.5337523f@inspiron>
     [not found]             ` <Pine.LNX.4.63.0605031242020.1846@pcgl.dsa-ac.de>
     [not found]               ` <20060503132301.52a75dcd@inspiron>
2006-05-05 18:43                 ` drivers/acorn/char/pcf8583.[hc] vs. RTC subsystem Guennadi Liakhovetski

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=20060331100425.001583000@towertech.it \
    --to=a.zummo@towertech.it \
    --cc=akpm@osdl.org \
    --cc=akpm@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yoichi_yuasa@tripeaks.co.jp \
    /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