All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2,1/1] package/fio: bump to version 3.28
Date: Sat, 18 Sep 2021 22:33:59 +0200	[thread overview]
Message-ID: <20210918203359.GS1053080@scaer> (raw)
In-Reply-To: <20210912164819.2164395-1-fontaine.fabrice@gmail.com>

Fabrice, All,

On 2021-09-12 18:48 +0200, Fabrice Fontaine spake thusly:
> This will fix the following build failure with kernel >= 5.14 thanks to
> https://github.com/axboe/fio/commit/382975557e632efb506836bc1709789e615c9094:
> 
> In file included from crc/../os/os.h:39,
>                  from crc/crc32c-arm64.c:2:
> crc/../os/os-linux.h:17:10: fatal error: linux/raw.h: No such file or directory
>    17 | #include <linux/raw.h>
>       |          ^~~~~~~~~~~~~
> 
> Fixes:
>  - http://autobuild.buildroot.org/results/d85c044263c76ff7ef0fe47921d893a472954da9
> 
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>

Applied to master, thanks.

Regards,
Yann E. MORIN.

> ---
> Changes v1 -> v2:
>  - Fix tarball hash
> 
>  package/fio/fio.hash | 2 +-
>  package/fio/fio.mk   | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/package/fio/fio.hash b/package/fio/fio.hash
> index 88319e4cc0..891ca4e40e 100644
> --- a/package/fio/fio.hash
> +++ b/package/fio/fio.hash
> @@ -1,4 +1,4 @@
>  # Locally computed
> -sha256  da9826f07a003656ea070d359c90f752db8c3216ced9ff865242eed1a1db93bc  fio-3.27.tar.gz
> +sha256  859dca5241e5494d86c4aa1531a984cc556789c78e56b30d6070acfbdd193a8c  fio-3.28.tar.gz
>  sha256  8177f97513213526df2cf6184d8ff986c675afb514d4e68a404010521b880643  COPYING
>  sha256  8a240c1ad13d1fe3e58588643d81d0695899be4a669fe6d8fafa76ca6a89db2c  MORAL-LICENSE
> diff --git a/package/fio/fio.mk b/package/fio/fio.mk
> index 12e2b2ab7c..13818b60fd 100644
> --- a/package/fio/fio.mk
> +++ b/package/fio/fio.mk
> @@ -4,7 +4,7 @@
>  #
>  ################################################################################
>  
> -FIO_VERSION = 3.27
> +FIO_VERSION = 3.28
>  FIO_SITE = http://brick.kernel.dk/snaps
>  FIO_LICENSE = GPL-2.0
>  FIO_LICENSE_FILES = COPYING MORAL-LICENSE
> -- 
> 2.33.0
> 
> _______________________________________________
> buildroot mailing list
> buildroot@lists.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@lists.buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2021-09-18 20:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-12 16:48 [Buildroot] [PATCH v2,1/1] package/fio: bump to version 3.28 Fabrice Fontaine
2021-09-18 20:33 ` Yann E. MORIN [this message]
2021-09-29 19:52 ` 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=20210918203359.GS1053080@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@buildroot.org \
    --cc=fontaine.fabrice@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.