Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Radu Moisan <radu.moisan@intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2] usbutils: Upgrade usbutils to upstream v006
Date: Fri, 03 Aug 2012 08:33:58 +0300	[thread overview]
Message-ID: <501B62C6.20205@intel.com> (raw)
In-Reply-To: <CAK18fxFW89ficqdXn-H2VOPApOUhaXH0yNOkK4xb3J1HtxfLnA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2164 bytes --]


On 08/02/2012 06:25 PM, Andrei Gherzan wrote:
> On Thu, Aug 2, 2012 at 3:06 PM, Radu Moisan <radu.moisan@intel.com 
> <mailto:radu.moisan@intel.com>> wrote:
>
>     Signed-off-by: Radu Moisan <radu.moisan@intel.com
>     <mailto:radu.moisan@intel.com>>
>     ---
>      .../usbutils/{usbutils_0.91.bb <http://usbutils_0.91.bb> =>
>     usbutils_006.bb <http://usbutils_006.bb>} |    7 +++----
>      1 file changed, 3 insertions(+), 4 deletions(-)
>      rename meta/recipes-bsp/usbutils/{usbutils_0.91.bb
>     <http://usbutils_0.91.bb> => usbutils_006.bb
>     <http://usbutils_006.bb>} (80%)
>
>     diff --git a/meta/recipes-bsp/usbutils/usbutils_0.91.bb
>     <http://usbutils_0.91.bb>
>     b/meta/recipes-bsp/usbutils/usbutils_006.bb <http://usbutils_006.bb>
>     similarity index 80%
>     rename from meta/recipes-bsp/usbutils/usbutils_0.91.bb
>     <http://usbutils_0.91.bb>
>     rename to meta/recipes-bsp/usbutils/usbutils_006.bb
>     <http://usbutils_006.bb>
>     index abe807c..c1c9fc0 100644
>     --- a/meta/recipes-bsp/usbutils/usbutils_0.91.bb
>     <http://usbutils_0.91.bb>
>     +++ b/meta/recipes-bsp/usbutils/usbutils_006.bb
>     <http://usbutils_006.bb>
>     @@ -7,19 +7,18 @@ LICENSE = "GPLv2+"
>      LIC_FILES_CHKSUM =
>     "file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f"
>
>      DEPENDS = "libusb zlib"
>     -PR = "r5"
>     +PR = "r0"
>
>      SRC_URI =
>     "${KERNELORG_MIRROR}/linux/utils/usb/usbutils/usbutils-${PV}.tar.gz \
>                 file://usb-devices-avoid-dependency-on-bash.patch \
>                 file://Fix-NULL-pointer-crash.patch"
>
>     -SRC_URI[md5sum] = "49de2403b40bf3a9863faaa8d3858deb"
>     -SRC_URI[sha256sum] =
>     "c122346b0225121bcf159abf804116f826a4a3462c94ce7b8871f7559e6b3a46"
>     +SRC_URI[md5sum] = "850790442f5eb487cdc7e35f8ee03e11"
>     +SRC_URI[sha256sum] =
>     "553270b4030f0844cb70aed57e61c7f10a7ed6641c3bed20249201cec9bcf122"
>
>      inherit autotools
>
>      do_install_append() {
>     -       ln -s ../sbin/lsusb ${D}${bindir}/lsusb
>
>
> This is not needed anymore?
>
No, it's already in place.

radu

[-- Attachment #2: Type: text/html, Size: 4436 bytes --]

      reply	other threads:[~2012-08-03  5:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-02 12:06 [PATCH v2] usbutils: Upgrade usbutils to upstream v006 Radu Moisan
2012-08-02 13:50 ` Koen Kooi
2012-08-02 13:55   ` Burton, Ross
2012-08-02 14:14     ` Koen Kooi
2012-08-02 15:24       ` Andrei Gherzan
2012-08-02 15:28       ` Paul Eggleton
2012-08-03 10:22         ` Koen Kooi
2012-08-02 15:25 ` Andrei Gherzan
2012-08-03  5:33   ` Radu Moisan [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=501B62C6.20205@intel.com \
    --to=radu.moisan@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