From: Saul Wold <saul.wold@intel.com>
To: Tom Zanussi <tom.zanussi@intel.com>
Cc: poky@yoctoproject.org
Subject: Re: [PATCH] put udev trigger fix into meta-intel laverne
Date: Thu, 10 Feb 2011 09:13:05 -0800 [thread overview]
Message-ID: <4D541CA1.8000500@intel.com> (raw)
In-Reply-To: <849307$bh0po3@azsmga001.ch.intel.com>
On 02/10/2011 08:30 AM, Tom Zanussi wrote:
> From: Tom Zanussi<tom.zanussi@intel.com>
>
> We can't do a laverne point release to include the udev trigger fix
> right now, but we still need it in the laverne BSP, so roll it into
> the layer instead.
>
> Please pull into meta-intel laverne.
>
Pulled into meta-intel
Thanks for the quick turn.
Sau!
> Pull URL: git://git.pokylinux.org/meta-intel.git
> Branch: tzanussi/apply-udev-trigger-for-laverne-here
> Browse:
> http://git.pokylinux.org/cgit.cgi/meta-intel/log/?h=tzanussi/apply-udev-trigger-for-laverne-here
>
> Tom Zanussi (1):
> meta-crownbay: apply init-live.sh coldplug udev trigger patch here
> instead
>
> ...01-init-live.sh-add-coldplug-udev-trigger.patch | 44 ++++++++++++++++++++
> .../initrdscripts/initramfs-live-boot_1.0.bbappend | 6 +++
> 2 files changed, 50 insertions(+), 0 deletions(-)
> create mode 100644 meta-crownbay/recipes-core/initrdscripts/initramfs-live-boot/0001-init-live.sh-add-coldplug-udev-trigger.patch
> create mode 100644 meta-crownbay/recipes-core/initrdscripts/initramfs-live-boot_1.0.bbappend
>
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
>
prev parent reply other threads:[~2011-02-10 17:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-10 16:30 [PATCH] put udev trigger fix into meta-intel laverne Tom Zanussi
2011-02-10 17:13 ` 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=4D541CA1.8000500@intel.com \
--to=saul.wold@intel.com \
--cc=poky@yoctoproject.org \
--cc=tom.zanussi@intel.com \
/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