Re: [PATCH 1/1] Update libusb1 from 1.0.19 to 1.0.20

From: Otavio Salvador <otavio.salvador@ossystems.com.br>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] Update libusb1 from 1.0.19 to 1.0.20
Date: Thu, 29 Oct 2015 10:37:08 -0200	[thread overview]
Message-ID: <CAP9ODKrj3XrhrUBjp7VssdqWbeMvKNm_iJSSQY0L7h-S7DmyLg@mail.gmail.com> (raw)
In-Reply-To: <1556288.oU3CJGhmjq@peggleto-mobl.ger.corp.intel.com>

On Thu, Oct 29, 2015 at 10:27 AM, Paul Eggleton
<paul.eggleton@linux.intel.com> wrote:
> On Thursday 29 October 2015 12:47:18 Jens Rehsack wrote:
>> > Am 08.10.2015 um 16:36 schrieb Jens Rehsack <rehsack@gmail.com>:
>> >
>> > This updates libusb1 from 1.0.19 to 1.0.20
>> >
>> > 2015-09-13: v1.0.20
>> > * Add Haiku support
>> > * Fix multiple memory and resource leaks (#16, #52, #76, #81)
>> > * Fix possible deadlock when executing transfer callback
>> > * New libusb_free_pollfds() API
>> > * Darwin: Fix devices not being detected on OS X 10.8 (#48)
>> > * Linux: Allow larger isochronous transfer submission (#23)
>> > * Windows: Fix broken builds Cygwin/MinGW builds and compiler warnings
>> > * Windows: Fix broken bus number lookup
>> > * Windows: Improve submission of control requests for composite devices
>> > * Examples: Add two-stage load support to fxload (#12)
>> > * Correctly report cancellations due to timeouts
>> > * Improve efficiency of event handling
>> > * Improve speed of transfer submission in multi-threaded environments
>> > * Various other bug fixes and improvements
>> > The (#xx) numbers are libusb issue numbers, see ie:
>> > https://github.com/libusb/libusb/issues/16
>> >
>> > Signed-off-by: Jens Rehsack <sno@netbsd.org>
>> > ---
>> > meta/recipes-support/libusb/{libusb1_1.0.19.bb => libusb1_1.0.20.bb} | 4
>> > ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
>> > rename meta/recipes-support/libusb/{libusb1_1.0.19.bb =>
>> > libusb1_1.0.20.bb} (85%)
>> >
>> > diff --git a/meta/recipes-support/libusb/libusb1_1.0.19.bb
>> > b/meta/recipes-support/libusb/libusb1_1.0.20.bb similarity index 85%
>> > rename from meta/recipes-support/libusb/libusb1_1.0.19.bb
>> > rename to meta/recipes-support/libusb/libusb1_1.0.20.bb
>> > index a20e1fc..21b8b45 100644
>> > --- a/meta/recipes-support/libusb/libusb1_1.0.19.bb
>> > +++ b/meta/recipes-support/libusb/libusb1_1.0.20.bb
>> > @@ -11,8 +11,8 @@ BBCLASSEXTEND = "native nativesdk"
>> > SRC_URI = "${SOURCEFORGE_MIRROR}/libusb/libusb-${PV}.tar.bz2 \
>> >
>> >           "
>> >
>> > -SRC_URI[md5sum] = "f9e2bb5879968467e5ca756cb4e1fa7e"
>> > -SRC_URI[sha256sum] =
>> > "6c502c816002f90d4f76050a6429c3a7e0d84204222cbff2dce95dd773ba6840"
>> > +SRC_URI[md5sum] = "1d4eb194eaaa2bcfbba28102768c7dbf"
>> > +SRC_URI[sha256sum] =
>> > "cb057190ba0a961768224e4dc6883104c6f945b2bf2ef90d7da39e7c1834f7ff"
>> >
>> > S = "${WORKDIR}/libusb-${PV}"
>>
>> Ping :)
>
> At this point in the release it's too late for version upgrades unless the
> upgrade fixes a critical issue and applying the patch to fix that issue is more
> risky than the upgrade. I should imagine Ross has this queued for master when
> the release happens and we diverge.

Due the memory leak fixes, I think we could consider the backport for
2.0.1 after it proves stable in master for some time.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750