From: "Gabor Z. Papp" <gzp@papp.hu>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev regression from 167 to 168 on notion ink adam
Date: Wed, 04 May 2011 16:31:31 +0000 [thread overview]
Message-ID: <x6aaf277h8@gzp> (raw)
In-Reply-To: <809580245.144501.1304521074555.JavaMail.fmail@mwmweb069>
* "Johannes Schauer" <j.schauer@email.de>:
| I had still an older rootfs of mine lying around with udev 167 which
| was working fine. After I upgraded it to 168 it showed the exact
| same behaviour as explained above.
Same happend to me with 2.6.27.x on x86, but I was lazy do debug it, since I
don't use it daily.
next prev parent reply other threads:[~2011-05-04 16:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-04 14:57 udev regression from 167 to 168 on notion ink adam Johannes Schauer
2011-05-04 15:20 ` Marco d'Itri
2011-05-04 16:03 ` Kay Sievers
2011-05-04 16:31 ` Gabor Z. Papp [this message]
2011-05-04 16:36 ` Kay Sievers
2011-05-04 18:39 ` Johannes Schauer
2011-05-05 8:33 ` Johannes Schauer
2011-05-05 9:33 ` Kay Sievers
2011-05-05 9:38 ` Kay Sievers
2011-05-05 9:56 ` Marco d'Itri
2011-05-05 10:06 ` Kay Sievers
2011-05-05 10:18 ` Marco d'Itri
2011-05-05 11:32 ` Johannes Schauer
2011-05-05 12:04 ` Johannes Schauer
2011-05-05 15:13 ` Kay Sievers
2011-05-05 15:37 ` Johannes Schauer
2011-05-05 15:42 ` Marco d'Itri
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=x6aaf277h8@gzp \
--to=gzp@papp.hu \
--cc=linux-hotplug@vger.kernel.org \
/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.