From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: Greg KH <gregkh@suse.de>
Cc: Simon Arlott <simon@fire.lp0.eu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: sysfs/udev broken in latest git?
Date: Tue, 24 Jul 2007 10:03:14 +0200 [thread overview]
Message-ID: <20070724100314.3c606131@gondolin.boeblingen.de.ibm.com> (raw)
In-Reply-To: <20070724072540.GA835@suse.de>
On Tue, 24 Jul 2007 00:25:40 -0700,
Greg KH <gregkh@suse.de> wrote:
> On Tue, Jul 24, 2007 at 07:39:38AM +0100, Simon Arlott wrote:
> > The following commit appears to break some of my udev rules (I don't
> > have the time to finish the bisect right now, but there's only four
> > changes showing in "git bisect visualize" - this one is tagged
> > bisect/bad, and the other three are docs/docs/unrelated).
> >
> > Neither of these symlinks get created by udev on kernels marked bad
> > (see bisect log below):
> >
> > ACTION=="add", \
> > KERNEL=="event*", \
> > SUBSYSTEM=="input", \
> > SYSFS{description}=="i8042 KBD port", \
> > NAME="input/%k", \
> > SYMLINK="input/i8042-kbd", \
> > MODE="0640", \
> > GROUP="event"
> >
> > ACTION=="add", \
> > KERNEL=="event*", \
> > SUBSYSTEM=="input", \
> > SYSFS{manufacturer}=="Logitech", \
> > SYSFS{product}=="USB-PS/2 Optical Mouse", \
> > NAME="input/%k", \
> > SYMLINK="input/logitech-mouse", \
> > MODE="0640", \
> > GROUP="event"
> Ugh, I thought this was all fixed up properly :(
I thought this as well :(
But I'm a bit confused: The patch in git has
+ /* only bus-device parents get a "device"-link */
+ if (dev->parent && dev->parent->bus) {
+ error = sysfs_create_link(&dev->kobj, &dev->parent->kobj,
+ "device");
and
- if (parent) {
- sysfs_create_link(&dev->kobj, &dev->parent->kobj,
- "device");
which really look like two different things. (My original patch didn't
have the check for the parent's bus.) Don't know what happened here :(
(Simon: Do the links reappear if you change
if (dev->parent && dev->parent->bus)
to
if (dev->parent)
in device_add_class_symlinks()?)
next prev parent reply other threads:[~2007-07-24 8:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-24 6:39 Simon Arlott
2007-07-24 7:25 ` Greg KH
2007-07-24 8:03 ` Cornelia Huck [this message]
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
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=20070724100314.3c606131@gondolin.boeblingen.de.ibm.com \
--to=cornelia.huck@de.ibm.com \
--cc=gregkh@suse.de \
--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
all inboxes | Powered by JetHome®