public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] libusb: Update to version 1.0.25
Date: Fri, 11 Feb 2022 10:19:02 +0100	[thread overview]
Message-ID: <8e9e7522-79ea-c848-664c-4eff852b120b@ipfire.org> (raw)
In-Reply-To: <20220209212916.2754129-1-adolf.belka@ipfire.org>

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

Hi Everyone,

Having submitted this patch I saw that there is a bug related to libusb 
(#12667) I don't know if this will fix the bug or not, although it does 
mention fixing a regression with some particular devices in the changelog.

Anyway, feel free to either use or ignore and drop this patch as 
appropriate to the bug activities.

Regards,

Adolf.

On 09/02/2022 22:29, Adolf Belka wrote:
> - Update from 1.0.24 to 1.0.25
> - Update of rootfile not required
> - Changelog
>     2022-01-31: v1.0.25
>       * Linux: Fix regression with some particular devices
>       * Linux: Fix regression with libusb_handle_events_timeout_completed()
>       * Linux: Fix regression with cpu usage in libusb_bulk_transfer
>       * Darwin (macOS): Add support for detaching kernel drivers with authorization.
>       * Darwin (macOS): Do not drop partial data on timeout.
>       * Darwin (macOS): Silence pipe error in set_interface_alt_setting().
>       * Windows: Fix HID backend missing byte
>       * Windows: Fix segfault with libusbk driver
>       * Windows: Fix regression when using libusb0 driver
>       * Windows: Support LIBUSB_TRANSFER_ADD_ZERO_PACKET on winusb
>       * New NO_DEVICE_DISCOVERY option replaces WEAK_AUTHORITY option
>       * Various other bug fixes and improvements
> 
> Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
> ---
>   lfs/libusb | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/lfs/libusb b/lfs/libusb
> index 6af376943..ec633ee20 100644
> --- a/lfs/libusb
> +++ b/lfs/libusb
> @@ -24,7 +24,7 @@
>   
>   include Config
>   
> -VER        = 1.0.24
> +VER        = 1.0.25
>   
>   THISAPP    = libusb-$(VER)
>   DL_FILE    = $(THISAPP).tar.bz2
> @@ -40,7 +40,7 @@ objects = $(DL_FILE)
>   
>   $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>   
> -$(DL_FILE)_MD5 = 5bc27df16155302f308d409e73589872
> +$(DL_FILE)_MD5 = 4d8d9aa4656ec1e97eda5ef8d2071aaf
>   
>   install : $(TARGET)
>   

-- 
Sent from my laptop

  parent reply	other threads:[~2022-02-11  9:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-09 21:29 Adolf Belka
2022-02-11  8:51 ` Peter Müller
2022-02-11  9:19 ` Adolf Belka [this message]
2022-02-11  9:22   ` Adolf Belka

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=8e9e7522-79ea-c848-664c-4eff852b120b@ipfire.org \
    --to=adolf.belka@ipfire.org \
    --cc=development@lists.ipfire.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