From: Peter Korsgaard <peter@korsgaard.com>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Gao Xiang <hsiangkao@aol.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/erofs-utils: bump to version 1.5
Date: Thu, 07 Jul 2022 15:13:59 +0200 [thread overview]
Message-ID: <87sfndoyjs.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20220703093952.1300768-1-fontaine.fabrice@gmail.com> (Fabrice Fontaine's message of "Sun, 3 Jul 2022 11:39:52 +0200")
>>>>> "Fabrice" == Fabrice Fontaine <fontaine.fabrice@gmail.com> writes:
> - Drop patches (already in version)
> - liberofs is now released under GPL-2.0+ OR Apache-2.0 license:
> https://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs-utils.git/commit/?id=49b344c5531a7819f282b0b1b6eb01682c0e41ae
> - This bump will fix the following build failure on or1k thanks to
> https://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs-utils.git/commit/?id=100cae2b98a70ac69ae7a09ed94f86ddf8c89fe2
> In file included from ../include/erofs/cache.h:11,
> from cache.c:9:
> ../include/erofs/internal.h:34:2: error: #error incompatible PAGE_SIZE is already defined
> 34 | #error incompatible PAGE_SIZE is already defined
> | ^~~~~
> https://lists.ozlabs.org/pipermail/linux-erofs/2022-June/006462.html
> Fixes:
> - http://autobuild.buildroot.org/results/755f8d736b8ad96b213bb3975b26f1143e60e5b5
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Committed, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-07-07 13:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-03 9:39 [Buildroot] [PATCH 1/1] package/erofs-utils: bump to version 1.5 Fabrice Fontaine
2022-07-05 1:09 ` Gao Xiang via buildroot
2022-07-07 13:13 ` Peter Korsgaard [this message]
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=87sfndoyjs.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--cc=hsiangkao@aol.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