linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: USB development list <linux-usb-devel@lists.sourceforge.net>,
	linux-kernel@vger.kernel.org
Subject: Re: Missing kobject release methods?
Date: Wed, 29 Oct 2003 14:59:22 -0800	[thread overview]
Message-ID: <20031029225922.GB1513@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0310271121350.679-100000@ida.rowland.org>

On Mon, Oct 27, 2003 at 11:31:44AM -0500, Alan Stern wrote:
> Greg:
> 
> For a long time, I've been getting debug warnings about missing release()  
> methods in various kobjects.  They come up because your usb-2.5 tree has
> DEBUG defined in a number of driver-model source files.

And because I have a "test for .release in a kobject" patch in my tree
to help me debug.  That's what you are seeing.

> It's not easy to track down exactly what the objects in question are;

Don't worry about these, they are all for things that are only
directories, and don't have release functions because they do not need
to at this time.  Pat is aware of these and someday we will divorce
kobjects from beeing needed just to create a subdirectory in sysfs.

These false warnings are the reason that patch never made it into the
main kernel tree, unlike the other .release checks in the driver model
code.

You can just disable that change in your copy of my tree if it's really
annoying you :)

thanks,

greg k-h

      reply	other threads:[~2003-10-29 23:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-27 16:31 Missing kobject release methods? Alan Stern
2003-10-29 22:59 ` Greg KH [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=20031029225922.GB1513@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=stern@rowland.harvard.edu \
    /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).