From: Greg KH <greg@kroah.com>
To: Aaron Gyes <floam@sh.nu>
Cc: Mathieu Segaud <matt@regala.cx>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.14-rc4-mm1: udev/sysfs wierdness
Date: Wed, 19 Oct 2005 16:44:29 -0700 [thread overview]
Message-ID: <20051019234429.GD18295@kroah.com> (raw)
In-Reply-To: <1129701608.10192.1.camel@localhost>
On Tue, Oct 18, 2005 at 11:00:08PM -0700, Aaron Gyes wrote:
> On Tue, 2005-10-18 at 20:44 -0700, Greg KH wrote:
> > 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.
>
> I applied that, and I still don't see the node being created.
Yeah, sorry.
You need a udev update. 071 has been released which should fix this
problem (fixes it for me.) Can you try that out?
thanks,
greg k-h
next prev parent reply other threads:[~2005-10-20 0:33 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
2005-10-19 6:00 ` Aaron Gyes
2005-10-19 23:44 ` Greg KH [this message]
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=20051019234429.GD18295@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox