public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	kay.sievers@vrfy.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Kobjects: drop child->parent ref at unregistration
Date: Tue, 27 Nov 2007 10:07:42 -0800	[thread overview]
Message-ID: <20071127180742.GA2768@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0711271235430.3037-100000@iolanthe.rowland.org>

On Tue, Nov 27, 2007 at 12:41:23PM -0500, Alan Stern wrote:
> On Tue, 27 Nov 2007, Greg KH wrote:
> 
> > For now, I'd recommend dropping it from your tree Andrew, as it might
> > cause odd issues on device removal (not quite sure though...)
> 
> But then there's the counter-argument: If the patch does cause any odd 
> issues to shake loose, learning about them in advance by exposing the 
> patch in the -mm tree would be worthwhile.
> 
> Sounds like it's time for an executive decision...  :-)

Heh.  I'm not ignoring the patch, and will apply it if I test it out and
see that it doesn't break anything.  Then I will let it bake in -mm for
a while.

I just don't want to rush it as this area of the kobject core is nasty
and full of tricks that I always forget.

Let me finish writing up this documentation on what I do remember and
then I'll attack the block device patch and this one.

thanks,

greg k-h

  reply	other threads:[~2007-11-27 18:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-19 15:53 [PATCH] Kobjects: drop child->parent ref at unregistration Alan Stern
2007-11-26 22:58 ` Andrew Morton
2007-11-27  2:29   ` Alan Stern
2007-11-27 17:01     ` Greg KH
2007-11-27 17:41       ` Alan Stern
2007-11-27 18:07         ` Greg KH [this message]
2007-11-27 20:31           ` Alan Stern
2007-11-29 21:14 ` patch kobject-drop-child-parent-ref-at-unregistration.patch added to gregkh-2.6 tree gregkh

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=20071127180742.GA2768@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@linux-foundation.org \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --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