From: Dongxiao Xu <dongxiao.xu@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1][PULL] Fix udevd launch issue
Date: Thu, 9 Jun 2011 09:08:31 +0800 [thread overview]
Message-ID: <cover.1307581528.git.dongxiao.xu@intel.com> (raw)
Hi Saul,
This commit fixes the udevd launch issue after system second boot. [YOCTO #1146].
Without udevd daemon, device nodes will not be created if dynamically insert a kernel module.
Please help to review and pull.
The following changes since commit 5af197b55a4b779f1ec93186f0723026949ba2b5:
cache: Implement multiple extra cache fields request support (2011-06-07 22:40:01 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib dxu4/bugfix
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=dxu4/bugfix
Dongxiao Xu (1):
udev: Fix udevd launch issue after system second boot
meta/recipes-core/udev/udev-164/init | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
next reply other threads:[~2011-06-09 1:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-09 1:08 Dongxiao Xu [this message]
2011-06-09 1:08 ` [PATCH 1/1] udev: Fix udevd launch issue after system second boot Dongxiao Xu
2011-06-09 6:15 ` [PATCH 0/1][PULL] Fix udevd launch issue Koen Kooi
2011-06-09 18:42 ` Saul Wold
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=cover.1307581528.git.dongxiao.xu@intel.com \
--to=dongxiao.xu@intel.com \
--cc=openembedded-core@lists.openembedded.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.