public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>,
	Martin Schwidefsky <schwidefsky@de.ibm.com>
Subject: Re: [Patch -mm 2/5] driver core: Introduce device_move(): move a device to a new parent.
Date: Tue, 14 Nov 2006 22:50:52 -0800	[thread overview]
Message-ID: <20061115065052.GC23810@kroah.com> (raw)
In-Reply-To: <20061114113208.74ec12c4@gondolin.boeblingen.de.ibm.com>

On Tue, Nov 14, 2006 at 11:32:08AM +0100, Cornelia Huck wrote:
> From: Cornelia Huck <cornelia.huck@de.ibm.com>
> 
> Provide a function device_move() to move a device to a new parent device. Add
> auxilliary functions kobject_move() and sysfs_move_dir().

At first glance, this looks sane, but for the kobject_move function, we
are not notifying userspace that something has changed here.

Is that ok?

How will udev and HAL handle something like this without being told
about it?  When the device eventually goes away, I think they will be
very confused.

thanks,

greg k-h

  reply	other threads:[~2006-11-15  7:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-14 10:32 [Patch -mm 2/5] driver core: Introduce device_move(): move a device to a new parent Cornelia Huck
2006-11-15  6:50 ` Greg KH [this message]
2006-11-15  7:28   ` Cornelia Huck
2006-11-15  8:44     ` Kay Sievers
2006-11-15  9:24       ` Cornelia Huck
2006-11-15  9:31         ` Kay Sievers
2006-11-15 10:11           ` Cornelia Huck
2006-11-15 16:44             ` Dmitry Torokhov
2006-11-15 17:23               ` Cornelia Huck
2006-11-15 17:39             ` Cornelia Huck

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=20061115065052.GC23810@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@osdl.org \
    --cc=cornelia.huck@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schwidefsky@de.ibm.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