All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Implement class_device_update_dev() function
Date: Thu, 6 Jul 2006 16:57:45 -0700	[thread overview]
Message-ID: <20060706235745.GA13548@kroah.com> (raw)
In-Reply-To: <1152226792.29643.8.camel@localhost>

On Fri, Jul 07, 2006 at 12:59:52AM +0200, Marcel Holtmann wrote:
> Hi Greg,
> 
> for the Bluetooth subsystem integration into the driver model it is
> required that we can update the device of a class device at any time.

You can?  Ick.

That messes with my "get rid of struct class_device" plans a bit...

> For the RFCOMM TTY device for example we create the TTY device and only
> when it got opened we create the Bluetooth connection. Once this new
> connection has been created we have a device to attach to the class
> device of the TTY.
> 
> I came up with the attached patch and it worked fine with the Bluetooth
> RFCOMM layer.

But userspace should also find out about this change, and this patch
prevents that from happening.  What about just tearing down the class
device and creating a new one?  That way userspace knows about the new
linkage properly, and any device naming and permission issues can be
handled anew?

thanks,

greg k-h

  reply	other threads:[~2006-07-07  0:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-06 22:59 Implement class_device_update_dev() function Marcel Holtmann
2006-07-06 23:57 ` Greg KH [this message]
2006-07-07  7:42   ` Marcel Holtmann
2006-07-08  0:26     ` Kay Sievers
2006-07-08  9:27       ` Marcel Holtmann
2006-07-08 13:00         ` Kay Sievers
2006-07-08 13:28           ` Marcel Holtmann
2006-07-08 17:27             ` Marcel Holtmann
2006-07-11 23:18     ` 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=20060706235745.GA13548@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.