From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Köry Maincent via buildroot" <buildroot@buildroot.org>
Cc: "Köry Maincent" <kory.maincent@bootlin.com>,
"Jens Kleintje" <scooby22@web.de>
Subject: Re: [Buildroot] [PATCH] package/gcnano-binaries: bump version to 6.4.13
Date: Thu, 4 Jan 2024 23:37:28 +0100 [thread overview]
Message-ID: <20240104233728.2a705e39@windsurf> (raw)
In-Reply-To: <20231121102632.74304-1-kory.maincent@bootlin.com>
On Tue, 21 Nov 2023 11:26:31 +0100
Köry Maincent via buildroot <buildroot@buildroot.org> wrote:
> From: Kory Maincent <kory.maincent@bootlin.com>
>
> Update to the latest version of the gcnano-binaries blobs, which are
> compatible with the last v6.1-stm32mp-r1 kernel from the
> STMicroelectronics BSP.
>
> The location of the driver has changed it is now in the
> gcnano-driver-stm32mp directory instead of an archive.
>
> The VERSION and PREFIX temporary variable in pkgconfig file came back
> therefore the sed replacement also came back.
>
> The EULA license file has changed due to copyright year update, so its
> hash has changed.
>
> Signed-off-by: Kory Maincent <kory.maincent@bootlin.com>
> ---
> package/gcnano-binaries/gcnano-binaries.hash | 4 ++--
> package/gcnano-binaries/gcnano-binaries.mk | 18 +++++++++++-------
> 2 files changed, 13 insertions(+), 9 deletions(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-01-04 22:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-21 10:26 [Buildroot] [PATCH] package/gcnano-binaries: bump version to 6.4.13 Köry Maincent via buildroot
2024-01-04 22:37 ` Thomas Petazzoni via buildroot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-16 22:14 Giulio Benetti
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=20240104233728.2a705e39@windsurf \
--to=buildroot@buildroot.org \
--cc=kory.maincent@bootlin.com \
--cc=scooby22@web.de \
--cc=thomas.petazzoni@bootlin.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