From: Jarkko Sakkinen via buildroot <buildroot@buildroot.org>
To: "Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
<buildroot@buildroot.org>
Cc: "Andy Yan" <andyshrk@gmail.com>, "Andy Yan" <andyshrk@163.com>,
"Aaron Sierra" <aaron@bubbl-tek.com>
Subject: Re: [Buildroot] [PATCH v1 1/1] package/iotools: Update to v1.8
Date: Wed, 06 Nov 2024 21:20:54 +0200 [thread overview]
Message-ID: <D5FC8F4N1HDQ.2JX7HPE33GN7L@kernel.org> (raw)
In-Reply-To: <20241106184841.1053511-1-andriy.shevchenko@linux.intel.com>
On Wed Nov 6, 2024 at 8:48 PM EET, Andy Shevchenko wrote:
> This is minor update to iotools to fix some issues Aaron noticed and
> addressed. The bigger change will come later with better integration
> with the regular build systems (CMake).
>
> Cc: Aaron Sierra <aaron@bubbl-tek.com>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
> package/iotools/iotools.hash | 2 +-
> package/iotools/iotools.mk | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/package/iotools/iotools.hash b/package/iotools/iotools.hash
> index 11d7ffb73e39..48d347bb3c11 100644
> --- a/package/iotools/iotools.hash
> +++ b/package/iotools/iotools.hash
> @@ -1,3 +1,3 @@
> # Locally computed
> -sha256 13b8b87c7d1f22b8d8f50c499af09f9414a0879d69c22393f1051ed4bf28f378 iotools-v1.7.tar.gz
> +sha256 9cb6184030b2e5c2e6a7c7a2d016d29d42d4075a77e1ba982bdc3cd919491faf iotools-v1.8.tar.gz
> sha256 ab15fd526bd8dd18a9e77ebc139656bf4d33e97fc7238cd11bf60e2b9b8666c6 COPYING
> diff --git a/package/iotools/iotools.mk b/package/iotools/iotools.mk
> index 03b87c89e9d0..f5e322eab818 100644
> --- a/package/iotools/iotools.mk
> +++ b/package/iotools/iotools.mk
> @@ -4,7 +4,7 @@
> #
> ################################################################################
>
> -IOTOOLS_VERSION = v1.7
> +IOTOOLS_VERSION = v1.8
> IOTOOLS_SITE = $(call github,andy-shev,iotools,$(IOTOOLS_VERSION))
> IOTOOLS_LICENSE = GPL-2.0+
> IOTOOLS_LICENSE_FILES = COPYING
Tested-by: Jarkko Sakkinen <jarkko@kernel.org>
I use this is my BR builds occasionally, thus tested the patch :-)
BR, Jarkko
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-11-06 19:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 18:48 [Buildroot] [PATCH v1 1/1] package/iotools: Update to v1.8 Andy Shevchenko
2024-11-06 19:20 ` Jarkko Sakkinen via buildroot [this message]
2024-11-08 21:58 ` Julien Olivain
2024-11-11 7:17 ` Andy Shevchenko
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=D5FC8F4N1HDQ.2JX7HPE33GN7L@kernel.org \
--to=buildroot@buildroot.org \
--cc=aaron@bubbl-tek.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andyshrk@163.com \
--cc=andyshrk@gmail.com \
--cc=jarkko@kernel.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