From: Adrian Bunk <bunk@stusta.de>
To: Alessandro Zummo <a.zummo@towertech.it>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 01/13] RTC Subsystem, library functions
Date: Sat, 4 Mar 2006 17:58:43 +0100 [thread overview]
Message-ID: <20060304165843.GD9295@stusta.de> (raw)
In-Reply-To: <20060304164248.171528000@towertech.it>
On Sat, Mar 04, 2006 at 05:42:48PM +0100, Alessandro Zummo wrote:
>...
> --- /dev/null 1970-01-01 00:00:00.000000000 +0000
> +++ linux-rtc/drivers/rtc/Makefile 2006-02-28 13:16:36.000000000 +0100
> @@ -0,0 +1,7 @@
> +#
> +# Makefile for RTC class/drivers.
> +#
> +
> +ifneq ($(CONFIG_RTC_LIB), n)
> +obj-y += rtc-lib.o
> +endif
> --- /dev/null 1970-01-01 00:00:00.000000000 +0000
> +++ linux-rtc/drivers/rtc/Kconfig 2006-02-28 13:16:36.000000000 +0100
> @@ -0,0 +1,6 @@
> +#
> +# RTC class/drivers configuration
> +#
> +
> +config RTC_LIB
> + bool
>...
What about
config RTC_LIB
tristate
and
obj-$(CONFIG_RTC_LIB) += rtc-lib.o
?
IOW:
Is there anything besides adding a MODULE_LICENSE("GPL"); required for
allowing an rtc-lib module?
> --- linux-rtc.orig/drivers/Makefile 2006-02-28 13:16:34.000000000 +0100
> +++ linux-rtc/drivers/Makefile 2006-02-28 13:16:36.000000000 +0100
> @@ -56,6 +56,7 @@ obj-$(CONFIG_USB_GADGET) += usb/gadget/
> obj-$(CONFIG_GAMEPORT) += input/gameport/
> obj-$(CONFIG_INPUT) += input/
> obj-$(CONFIG_I2O) += message/
> +obj-y += rtc/
>...
obj-$(CONFIG_RTC_LIB) += rtc/
should be possible since RTC_CLASS select's RTC_LIB.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2006-03-04 16:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-04 16:42 [PATCH 00/13] RTC subsystem Alessandro Zummo
2006-03-04 16:42 ` [PATCH 01/13] RTC Subsystem, library functions Alessandro Zummo
2006-03-04 16:58 ` Adrian Bunk [this message]
2006-03-04 17:12 ` Alessandro Zummo
2006-03-04 17:20 ` Adrian Bunk
2006-03-04 16:42 ` [PATCH 02/13] RTC subsystem, ARM cleanup Alessandro Zummo
2006-03-04 16:42 ` [PATCH 03/13] RTC subsystem, MIPS cleanup Alessandro Zummo
2006-03-04 16:42 ` [PATCH 04/13] RTC subsystem, class Alessandro Zummo
2006-03-04 17:08 ` Adrian Bunk
2006-03-04 17:46 ` Alessandro Zummo
2006-03-04 17:53 ` Adrian Bunk
2006-03-04 18:04 ` Alessandro Zummo
2006-03-04 16:42 ` [PATCH 05/13] RTC subsystem, I2C cleanup Alessandro Zummo
2006-03-04 16:42 ` [PATCH 06/13] RTC subsystem, sysfs interface Alessandro Zummo
2006-03-04 16:42 ` [PATCH 07/13] RTC subsystem, proc interface Alessandro Zummo
2006-03-04 16:42 ` [PATCH 08/13] RTC subsystem, dev interface Alessandro Zummo
2006-03-04 16:42 ` [PATCH 09/13] RTC subsystem, X1205 driver Alessandro Zummo
2006-03-04 16:42 ` [PATCH 10/13] RTC subsystem, test device/driver Alessandro Zummo
2006-03-04 16:42 ` [PATCH 11/13] RTC subsystem, DS1672 driver Alessandro Zummo
2006-03-04 16:42 ` [PATCH 12/13] RTC subsystem, PCF8563 driver Alessandro Zummo
2006-03-04 16:43 ` [PATCH 13/13] RTC subsystem, RS5C372 driver Alessandro Zummo
-- strict thread matches above, loose matches on Subject: below --
2006-02-26 23:14 [PATCH 00/13] RTC subsystem Alessandro Zummo
2006-02-26 23:14 ` [PATCH 01/13] RTC Subsystem, library functions Alessandro Zummo
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=20060304165843.GD9295@stusta.de \
--to=bunk@stusta.de \
--cc=a.zummo@towertech.it \
--cc=linux-kernel@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