From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: "wangmy" <wangmy@fujitsu.com>
Cc: <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] btrfs-tools: upgrade 5.16.2 -> 5.18
Date: Mon, 30 May 2022 22:48:38 +0200 [thread overview]
Message-ID: <20220530224838.73d1009e@melee> (raw)
In-Reply-To: <1653892850-23554-2-git-send-email-wangmy@fujitsu.com>
Hi wangmy,
Il giorno Mon, 30 May 2022 14:40:48 +0800
"wangmy" <wangmy@fujitsu.com> ha scritto:
> lzo-option.patch
> removed since it's included in 5.18.
>
> Changelog:
> ==========
> fixes:
> dump-tree: don't print traling zeros in checksums
> recognize paused balance as exclusive operation state, allow to start device add
> convert: properly initialize target filesystem label
> mkfs: don't create free space bitmaps for empty filesystem
> restore: make lzo support build-time configurable, print supported compression in help text
> update kernel-lib sources
> other:
> documentation updates, finish conversion to RST, CHANGES and INSTALL could be included into RST
> fix build detection of experimental mode
> new tests
>
> Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
This patch triggers a build failure:
configure: error: cannot find sphinx-build, cannot build documentation
https://autobuilder.yoctoproject.org/typhoon/#/builders/108/builds/3051/steps/11/logs/errors
https://autobuilder.yoctoproject.org/typhoon/#/builders/108/builds/3051/steps/11/logs/stdio
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2022-05-30 20:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-30 6:40 [OE-core] [PATCH] logrotate: upgrade 3.19.0 -> 3.20.1 Wang Mingyu
2022-05-30 6:40 ` [OE-core] [PATCH] btrfs-tools: upgrade 5.16.2 -> 5.18 Wang Mingyu
2022-05-30 20:48 ` Luca Ceresoli [this message]
2022-05-30 6:40 ` [OE-core] [PATCH] dpkg: upgrade 1.21.7 -> 1.21.8 Wang Mingyu
2022-05-30 6:40 ` [OE-core] [PATCH] repo: upgrade 2.25 -> 2.26 Wang Mingyu
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=20220530224838.73d1009e@melee \
--to=luca.ceresoli@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=wangmy@fujitsu.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