From: Adrian Bunk <bunk@stusta.de>
To: Greg KH <greg@kroah.com>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] deprecate EXPORT_SYMBOL(do_settimeofday)
Date: Sat, 26 Feb 2005 18:13:25 +0100 [thread overview]
Message-ID: <20050226171325.GO3311@stusta.de> (raw)
In-Reply-To: <20050226164613.E7151@flint.arm.linux.org.uk>
On Sat, Feb 26, 2005 at 04:46:13PM +0000, Russell King wrote:
>...
> There are a number of ARM platforms which use a Ricoh RTC chip, and
> the driver for this will live in drivers/i2c/chips/ricoh-rtc.c. This
> is a stand alone driver in its own sense, handling the power management
> issues (saving the time offset/restoring the time) and setting the
> system time upon its initialisation. (In turn, this requires some i2c
> patches which add power management to the i2c subsystem to be merged
> first.)
>
> It's already used in some ARM platforms, including one which I was
> involved in. It just hasn't been merged.
>
> As far as drivers/acorn/char i2c rtc stuff goes, I plan to make this
> a full and proper i2c citizen, so adding breakage to the Kconfig with
> random select statements for publically viewable symbols isn't the
> way to go.
You call it "breakage" because you have a relatively dogmatic view
regarding the selection of user visible symbols.
Other people care more about the usability of the kernel config system,
and therefore a select of one of the I2C* options is quite common from
both outside and inside the i2c subsystem.
There are two possbile situations:
- these RTC drivers are nice add-ons that could be shown if all
required I2C* options are already enabled
- these RTC drivers are pretty essential and should really be enabled
on the platforms they are for
Which of these two cases describes the situation of these RTC drivers?
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:[~2005-02-26 17:13 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-24 23:37 [2.6 patch] unexport do_settimeofday Adrian Bunk
2005-02-25 5:24 ` Andrew Morton
2005-02-25 8:02 ` Arjan van de Ven
2005-02-25 8:28 ` Andrew Morton
2005-02-25 8:47 ` Bartlomiej Zolnierkiewicz
2005-02-25 9:26 ` Andreas Dilger
2005-02-25 9:33 ` Arjan van de Ven
2005-02-25 9:46 ` Andrew Morton
2005-02-27 22:44 ` Christoph Hellwig
2005-02-25 21:43 ` Adrian Bunk
2005-02-25 21:55 ` Andrew Morton
2005-02-25 23:02 ` Adrian Bunk
2005-02-25 23:20 ` Andrew Morton
2005-02-26 10:01 ` Arjan van de Ven
2005-02-26 15:28 ` Adrian Bunk
2005-02-26 15:22 ` Adrian Bunk
2005-02-26 13:33 ` [2.6 patch] deprecate EXPORT_SYMBOL(do_settimeofday) Adrian Bunk
2005-02-26 13:37 ` YOSHIFUJI Hideaki / 吉藤英明
2005-02-26 13:38 ` YOSHIFUJI Hideaki / 吉藤英明
2005-02-26 14:46 ` Russell King
2005-02-26 16:23 ` Adrian Bunk
2005-02-26 16:46 ` Russell King
2005-02-26 17:13 ` Adrian Bunk [this message]
2005-02-26 17:20 ` Russell King
2005-02-27 0:28 ` Adrian Bunk
2005-02-26 17:29 ` Russell King
2005-02-27 0:43 ` Adrian Bunk
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=20050226171325.GO3311@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--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