linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alessandro Zummo <alessandro.zummo@towertech.it>
To: Dmitry Torokhov <dtor_core@ameritech.net>
Cc: Alessandro Zummo <a.zummo@towertech.it>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/8] RTC subsystem, proc interface
Date: Mon, 9 Jan 2006 03:04:33 +0100	[thread overview]
Message-ID: <20060109030433.581c49e7@inspiron> (raw)
In-Reply-To: <200601082056.30227.dtor_core@ameritech.net>

On Sun, 8 Jan 2006 20:56:29 -0500
Dmitry Torokhov <dtor_core@ameritech.net> wrote:

> > +static void rtc_proc_remove_device(struct class_device *class_dev,
> > +                                             struct class_interface *class_intf)
> > +{
> > +       down(&rtc_sem);
> > +       if (rtc_dev == class_dev) {
> > +               remove_proc_entry("driver/rtc", NULL);
> > +               rtc_dev = NULL;
> > +       }
> > +       up(&rtc_sem);
> > +}
> 
> What if I happen to remove (unregister) rtc devices in order other
> than they were registered in? You need a counter there instead of
> storing the first device created.

 Only the first device that registers will get the /proc/driver/rtc
 entry, which will be removed when the driver unregisters.

 /proc/driver/rtc is a legacy interface, thus supporting it
 for more than one RTC is useless. Any system that uses
 more than one RTCs should access them via /dev/rtcX or
 via sysfs.


-- 

 Best regards,

 Alessandro Zummo,
  Tower Technologies - Turin, Italy

  http://www.towertech.it


  parent reply	other threads:[~2006-01-09  2:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-08 23:12 [PATCH 0/8] RTC subsystem Alessandro Zummo
2006-01-08 23:12 ` [PATCH 1/8] RTC subsystem, class Alessandro Zummo
2006-01-08 23:12 ` [PATCH 2/8] RTC subsystem, ARM cleanup Alessandro Zummo
2006-01-08 23:12 ` [PATCH 3/8] RTC subsystem, sysfs interface Alessandro Zummo
     [not found]   ` <200601082102.40992.dtor_core@ameritech.net>
2006-01-09  2:13     ` Alessandro Zummo
2006-01-08 23:12 ` [PATCH 4/8] RTC subsystem, proc interface Alessandro Zummo
     [not found]   ` <200601082056.30227.dtor_core@ameritech.net>
2006-01-09  2:04     ` Alessandro Zummo [this message]
2006-01-09  2:50       ` Dmitry Torokhov
2006-01-08 23:12 ` [PATCH 5/8] RTC subsystem, dev interface Alessandro Zummo
2006-01-09  2:50   ` Dmitry Torokhov
2006-01-09  3:12     ` Alessandro Zummo
2006-01-09  6:39       ` Dmitry Torokhov
2006-01-09  9:14         ` Alessandro Zummo
2006-01-08 23:12 ` [PATCH 6/8] RTC subsystem, X1205 driver Alessandro Zummo
2006-01-08 23:12 ` [PATCH 7/8] RTC subsystem, test device/driver Alessandro Zummo
2006-01-08 23:12 ` [PATCH 8/8] RTC subsystem, DS1672 driver 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=20060109030433.581c49e7@inspiron \
    --to=alessandro.zummo@towertech.it \
    --cc=a.zummo@towertech.it \
    --cc=dtor_core@ameritech.net \
    --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;
as well as URLs for NNTP newsgroup(s).