From: Greg KH <gregkh@suse.de>
To: Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: Kay Sievers <kay.sievers@vrfy.org>,
Simon Arlott <simon@fire.lp0.eu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: sysfs/udev broken in 2.6.23-rc1 [input, i2c, ...] (Was: sysfs/udev broken in latest git?)
Date: Wed, 25 Jul 2007 17:11:45 -0700 [thread overview]
Message-ID: <20070726001145.GC21056@suse.de> (raw)
In-Reply-To: <20070725095808.09b2cc2a@gondolin.boeblingen.de.ibm.com>
On Wed, Jul 25, 2007 at 09:58:08AM +0200, Cornelia Huck wrote:
> On Wed, 25 Jul 2007 02:19:18 +0200,
> "Kay Sievers" <kay.sievers@vrfy.org> wrote:
>
> > > >> Removing the dev->parent->bus check fixes it:
> >
> > Yes, let's remove the check, I will check now if we possibly need to
> > fix more than this or only the block-device patch.
>
> It seems this is the only place we check for dev->parent->bus in the
> current git tree.
>
> Patch below.
Thanks for figuring this out, I'll add this to my tree.
So what is the input layer doing so differently from everyone else here?
Is it correct? (sorry, am at a conference this week, so can't dig into
it as much as I would like to until Friday...)
thanks,
greg k-h
next prev parent reply other threads:[~2007-07-26 0:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-24 6:39 sysfs/udev broken in latest git? Simon Arlott
2007-07-24 7:25 ` Greg KH
2007-07-24 8:03 ` Cornelia Huck
2007-07-24 8:46 ` Greg KH
2007-07-24 9:20 ` Kay Sievers
2007-07-24 11:49 ` Simon Arlott
2007-07-24 11:55 ` Kay Sievers
2007-07-24 12:00 ` Simon Arlott
2007-07-24 12:54 ` Cornelia Huck
2007-07-24 16:28 ` sysfs/udev broken in 2.6.23-rc1 [input, i2c, ...] (Was: sysfs/udev broken in latest git?) Simon Arlott
2007-07-24 16:34 ` Kay Sievers
2007-07-24 16:57 ` Simon Arlott
2007-07-25 0:19 ` Kay Sievers
2007-07-25 7:58 ` Cornelia Huck
2007-07-26 0:11 ` Greg KH [this message]
2007-07-26 0:17 ` Kay Sievers
2007-07-30 19:12 ` patch driver-core-revert-device-link-creation-check.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=20070726001145.GC21056@suse.de \
--to=gregkh@suse.de \
--cc=cornelia.huck@de.ibm.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=simon@fire.lp0.eu \
/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