From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2] udev-164: fixup "don't hardcode path to pidof"
Date: Tue, 13 Mar 2012 09:30:02 -0700 [thread overview]
Message-ID: <4F5F760A.3020607@linux.intel.com> (raw)
In-Reply-To: <1331241861-15372-1-git-send-email-obi@opendreambox.org>
On 03/08/2012 01:24 PM, Andreas Oberritter wrote:
> * Remove -e shell option, because pidof may return nonzero.
>
> Signed-off-by: Andreas Oberritter<obi@opendreambox.org>
> ---
> * Of course I forgot to bump PR.
>
> meta/recipes-core/udev/udev/init | 2 +-
> meta/recipes-core/udev/udev_164.bb | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/meta/recipes-core/udev/udev/init b/meta/recipes-core/udev/udev/init
> index f9e9014..d521685 100644
> --- a/meta/recipes-core/udev/udev/init
> +++ b/meta/recipes-core/udev/udev/init
> @@ -1,4 +1,4 @@
> -#!/bin/sh -e
> +#!/bin/sh
>
> ### BEGIN INIT INFO
> # Provides: udev
> diff --git a/meta/recipes-core/udev/udev_164.bb b/meta/recipes-core/udev/udev_164.bb
> index d661044..c5813ec 100644
> --- a/meta/recipes-core/udev/udev_164.bb
> +++ b/meta/recipes-core/udev/udev_164.bb
> @@ -1,6 +1,6 @@
> include udev.inc
>
> -PR = "r12"
> +PR = "r13"
>
> SRC_URI += "file://udev-166-v4l1-1.patch"
>
Merged into OE-Core
Thanks
Sau!
prev parent reply other threads:[~2012-03-13 16:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-08 21:24 [PATCH v2] udev-164: fixup "don't hardcode path to pidof" Andreas Oberritter
2012-03-13 16:30 ` 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=4F5F760A.3020607@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