From: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
To: jengelh@computergmbh.de
Cc: david-b@pacbell.net, a.zummo@towertech.it,
linux-kernel@vger.kernel.org, rtc-linux@googlegroups.com,
dbrownell@users.sourceforge.net
Subject: Re: [PATCH] rtc: Make rtc-ds1742 driver hotplug-aware
Date: Sat, 18 Aug 2007 01:04:12 +0900 (JST) [thread overview]
Message-ID: <20070818.010412.72709547.anemo@mba.ocn.ne.jp> (raw)
In-Reply-To: <Pine.LNX.4.64.0708171736170.30502@fbirervta.pbzchgretzou.qr>
On Fri, 17 Aug 2007 17:37:01 +0200 (CEST), Jan Engelhardt <jengelh@computergmbh.de> wrote:
> >Most busses don't have managed device IDs like PCI, USB, or PNP.
> >
> >The platform, spi, and i2c busses use the driver name, which is
> >obviously managed within the scope of all Linux drivers.
> >
> Yeah but that does not tell me why it needs the ds1742 alias
> if scripts (whatever they use to discover it) could modprobe rtc-ds1742
> instead.
Well, the rtc-ds1742 platform driver uses a string "ds1742" for its
platform_driver definition.
static struct platform_driver ds1742_rtc_driver = {
.probe = ds1742_rtc_probe,
.remove = __devexit_p(ds1742_rtc_remove),
.driver = {
.name = "ds1742",
.owner = THIS_MODULE,
},
};
We can change the name string and all definitions of "ds1742" platform
device instead of adding MODULE_ALIAS. It is easy since there are
only a few users in kernel. If that was preferred, I can rewrite this
patch.
---
Atsushi Nemoto
prev parent reply other threads:[~2007-08-17 16:03 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-16 16:06 Atsushi Nemoto
2007-08-17 10:59 ` Jan Engelhardt
2007-08-17 15:23 ` David Brownell
2007-08-17 15:37 ` Jan Engelhardt
2007-08-17 16:02 ` David Brownell
2007-08-17 16:15 ` Atsushi Nemoto
2007-08-17 16:26 ` David Brownell
2007-08-17 16:32 ` Kay Sievers
2007-08-17 16:55 ` David Brownell
2007-08-17 17:18 ` Kay Sievers
2007-08-17 19:50 ` David Brownell
2007-08-17 19:52 ` Jan Engelhardt
2007-08-17 20:20 ` David Brownell
2007-08-18 2:40 ` Kay Sievers
2007-08-18 4:06 ` David Brownell
2007-08-18 10:45 ` Kay Sievers
2007-08-20 1:44 ` legacy platform drivers and hotplugging David Brownell
2007-08-20 2:02 ` Atsushi Nemoto
2007-08-20 9:51 ` Kay Sievers
2007-08-19 12:57 ` [PATCH] rtc: Make rtc-ds1742 driver hotplug-aware Atsushi Nemoto
2007-08-19 21:45 ` Kay Sievers
2007-08-20 1:48 ` David Brownell
2007-08-20 2:02 ` David Brownell
2007-08-20 2:16 ` Atsushi Nemoto
2007-08-17 16:04 ` Atsushi Nemoto [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=20070818.010412.72709547.anemo@mba.ocn.ne.jp \
--to=anemo@mba.ocn.ne.jp \
--cc=a.zummo@towertech.it \
--cc=david-b@pacbell.net \
--cc=dbrownell@users.sourceforge.net \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rtc-linux@googlegroups.com \
/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
all inboxes | Powered by JetHome®