public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor_core@ameritech.net>
To: linux-kernel@vger.kernel.org
Cc: Greg KH <greg@kroah.com>
Subject: Re: [PATCH] Driver Core patches for 2.6.7
Date: Tue, 22 Jun 2004 18:21:01 -0500	[thread overview]
Message-ID: <200406221821.02128.dtor_core@ameritech.net> (raw)
In-Reply-To: <1087926108744@kroah.com>

On Tuesday 22 June 2004 12:41 pm, Greg KH wrote:

>  
>  void class_unregister(struct class * cls)
>  {
>  	pr_debug("device class '%s': unregistering\n",cls->name);
> +	remove_class_attrs(cls);
>  	subsystem_unregister(&cls->subsys);
>  }
>  

Question: is it necessary to call remove_class_attrs? I thought that sysfs
automatically destroys all children when parent is destroyed? Am I imagining
things?
 
-- 
Dmitry

  parent reply	other threads:[~2004-06-22 23:24 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-22 17:19 [BK PATCH] Driver Core patches for 2.6.7 Greg KH
2004-06-22 17:41 ` [PATCH] " Greg KH
2004-06-22 17:41   ` Greg KH
2004-06-22 17:41     ` Greg KH
2004-06-22 17:41       ` Greg KH
2004-06-22 17:41         ` Greg KH
2004-06-22 17:41           ` Greg KH
2004-06-22 17:41             ` Greg KH
2004-06-22 17:41               ` Greg KH
2004-06-22 17:41                 ` Greg KH
2004-06-22 17:41                   ` Greg KH
2004-06-22 17:41                     ` Greg KH
2004-06-22 17:41                       ` Greg KH
2004-06-22 17:41                         ` Greg KH
2004-06-22 17:41                           ` Greg KH
2004-06-22 17:41                             ` Greg KH
2004-06-22 17:41                               ` Greg KH
2004-06-22 17:41                                 ` Greg KH
2004-06-22 17:41                                   ` Greg KH
2004-06-22 17:41                                     ` Greg KH
2004-06-22 17:41                                       ` Greg KH
2004-06-22 17:41                                         ` Greg KH
2004-06-22 17:41                                           ` Greg KH
2004-06-22 17:41                                             ` Greg KH
2004-06-22 17:41                                               ` Greg KH
2004-06-22 17:41                                                 ` Greg KH
2004-06-22 17:41                                                   ` Greg KH
2004-06-22 17:41                                                     ` Greg KH
2004-06-22 17:41                                                       ` Greg KH
2004-06-22 17:41                                                         ` Greg KH
2004-06-22 17:41                                                           ` Greg KH
2004-06-22 17:41                                                             ` Greg KH
2004-06-22 17:41                                                               ` Greg KH
2004-06-22 17:41                                                                 ` Greg KH
2004-06-22 17:41                                                                   ` Greg KH
2004-06-22 17:41                                                                     ` Greg KH
2004-06-22 23:21         ` Dmitry Torokhov [this message]
2004-06-22 23:31           ` Greg KH
2004-06-22 23:44             ` Dmitry Torokhov
2004-06-22 23:51               ` Greg KH

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=200406221821.02128.dtor_core@ameritech.net \
    --to=dtor_core@ameritech.net \
    --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