Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/1][PULL] Fix udevd launch issue
Date: Thu, 09 Jun 2011 11:42:34 -0700	[thread overview]
Message-ID: <4DF1141A.904@linux.intel.com> (raw)
In-Reply-To: <cover.1307581528.git.dongxiao.xu@intel.com>

On 06/08/2011 06:08 PM, Dongxiao Xu wrote:
> 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(-)
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>


Merged into OE-Core

Thanks
	Sau!



      parent reply	other threads:[~2011-06-09 18:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-09  1:08 [PATCH 0/1][PULL] Fix udevd launch issue Dongxiao Xu
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 [this message]

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=4DF1141A.904@linux.intel.com \
    --to=sgw@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox