Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Kris Bahnsen <kris@embeddedTS.com>
Cc: Ludovic Desroches <ludovic.desroches@microchip.com>,
	Mark Featherston <mark@embeddedTS.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/wilc-firmware: bump to 16.1
Date: Thu, 11 May 2023 22:18:45 +0200	[thread overview]
Message-ID: <20230511201845.GL252090@scaer> (raw)
In-Reply-To: <20230511175913.2360697-1-kris@embeddedTS.com>

Kris, All,

On 2023-05-11 10:59 -0700, Kris Bahnsen via buildroot spake thusly:
> According to release notes from Microchip, this fixes a memory
> leak in AP modes, fixes a failure with an undisclosed but specific
> AP, and re-certified with WFA for WILC1000.
> 
> Signed-off-by: Kris Bahnsen <kris@embeddedTS.com>

Applied to master, thanks.

Regards,
Yann E. MORIN.

> ---
>  package/wilc-firmware/wilc-firmware.hash | 2 +-
>  package/wilc-firmware/wilc-firmware.mk   | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/package/wilc-firmware/wilc-firmware.hash b/package/wilc-firmware/wilc-firmware.hash
> index 6e7850df16..802cb4f9b1 100644
> --- a/package/wilc-firmware/wilc-firmware.hash
> +++ b/package/wilc-firmware/wilc-firmware.hash
> @@ -1,3 +1,3 @@
>  # Locally calculated
> -sha256  2c2e2927a65fe4d7ec2f9872fca35c6b7bf12090ac62116d63c5f17b95a3a786  wilc-firmware-wilc_linux_15_7.tar.gz
> +sha256  a06a6a46e03ca00d35da220f7a9f353cc650e5e5657a7988ea732913ad26d9a0  wilc-firmware-wilc_linux_16_1.tar.gz
>  sha256  71355eee947a312594dbdaac039827544f93d23949b65c356b7b0ce09e2600fb  LICENSE.wilc_fw
> diff --git a/package/wilc-firmware/wilc-firmware.mk b/package/wilc-firmware/wilc-firmware.mk
> index e31829d430..12c825cf92 100644
> --- a/package/wilc-firmware/wilc-firmware.mk
> +++ b/package/wilc-firmware/wilc-firmware.mk
> @@ -4,7 +4,7 @@
>  #
>  ################################################################################
>  
> -WILC_FIRMWARE_VERSION = wilc_linux_15_7
> +WILC_FIRMWARE_VERSION = wilc_linux_16_1
>  WILC_FIRMWARE_SITE = $(call github,linux4wilc,firmware,$(WILC_FIRMWARE_VERSION))
>  
>  WILC_FIRMWARE_LICENSE = PROPRIETARY
> -- 
> 2.40.1
> 
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2023-05-11 20:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-11 17:59 [Buildroot] [PATCH 1/1] package/wilc-firmware: bump to 16.1 Kris Bahnsen via buildroot
2023-05-11 20:18 ` Yann E. MORIN [this message]
2023-06-12 15:59 ` Peter Korsgaard

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=20230511201845.GL252090@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@buildroot.org \
    --cc=kris@embeddedTS.com \
    --cc=ludovic.desroches@microchip.com \
    --cc=mark@embeddedTS.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