All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Mathieu Segaud <matt@regala.cx>
Cc: Aaron Gyes <floam@sh.nu>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.14-rc4-mm1: udev/sysfs wierdness
Date: Tue, 18 Oct 2005 20:44:27 -0700	[thread overview]
Message-ID: <20051019034427.GA15940@kroah.com> (raw)
In-Reply-To: <87r7ajdy4v.fsf@barad-dur.minas-morgul.org>

On Tue, Oct 18, 2005 at 10:31:44AM +0200, Mathieu Segaud wrote:
> Greg KH <greg@kroah.com> disait derni??rement que :
> 
> > On Mon, Oct 17, 2005 at 10:50:03PM -0700, Greg KH wrote:
> >> On Mon, Oct 17, 2005 at 09:35:13PM -0700, Aaron Gyes wrote:
> >> > For some reason this rule stopped working:
> >> > 
> >> > KERNEL=="event*", SYSFS{manufacturer}="Logitech", SYSFS{product}="USB
> >> > Receiver", NAME="input/mx1000", MODE="0644"
> >> > 
> >> > Did stuff in /sys/ change? Do I need to change all my rules to make up
> >> > for this? udevs fault? I do have the correct /dev/input/event0 node.
> >> 
> >> You have that node?  That's a good start :)
> >> 
> >> I think the "name" might have changed, it looks like I messed that up
> >> somehow.  What does:
> >> 	 udevinfo -p /sys/class/input/input0/event0/ -a
> >> 
> >> show (or whatever that sysfs path is.)
> >> 
> >> Oops, heh, that dies on my box too.  Ok, I think that's the issue,
> >> sorry.  I'm working on it...
> >
> > Can you try the patch below to see if that fixes the issue?  That should
> > keep udevinfo from dieing.
> 
> huh, it doesn't apply to 2.6.14-rc4-mm1....
> for which tree is it exactly ?
> 
> patching file drivers/input/input.c
> Hunk #1 succeeded at 641 (offset 119 lines).
> Hunk #2 FAILED at 818.
> Hunk #3 succeeded at 769 (offset 33 lines).
> 1 out of 3 hunks FAILED -- saving rejects to file drivers/input/input.c.rej

I was against my latest tree, which is on kernel.org.  Someone already
posted an updated patch on lkml if you can't get that second hunk to
apply.

thanks,

greg k-h

  reply	other threads:[~2005-10-19  3:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-18  4:35 2.6.14-rc4-mm1: udev/sysfs wierdness Aaron Gyes
2005-10-18  5:50 ` Greg KH
2005-10-18  6:57   ` Greg KH
2005-10-18  8:31     ` Mathieu Segaud
2005-10-19  3:44       ` Greg KH [this message]
2005-10-19  6:00         ` Aaron Gyes
2005-10-19 23:44           ` Greg KH
2005-10-20  3:34             ` Aaron Gyes
2005-10-20  3:50               ` Greg KH
2005-10-19  8:21         ` Mathieu Segaud

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=20051019034427.GA15940@kroah.com \
    --to=greg@kroah.com \
    --cc=floam@sh.nu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt@regala.cx \
    /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.