From: Oleksii Kurochko <oleksii.kurochko@gmail.com>
To: Anthony PERARD <anthony@xenproject.org>,
Andrew Cooper <andrew.cooper3@citrix.com>
Cc: xen-devel@lists.xenproject.org, Jan Beulich <jbeulich@suse.com>,
Anthony PERARD <anthony.perard@vates.tech>
Subject: Re: [XEN PATCH for-4.21] tools: require at least json-c 0.15
Date: Thu, 23 Oct 2025 17:22:38 +0200 [thread overview]
Message-ID: <d9924b94-36d0-4d7e-9a9b-bd4ea38f538d@gmail.com> (raw)
In-Reply-To: <aPpD_G_oULdfeWbf@l14>
[-- Attachment #1: Type: text/plain, Size: 2252 bytes --]
On 10/23/25 5:04 PM, Anthony PERARD wrote:
> On Thu, Oct 23, 2025 at 03:45:55PM +0100, Andrew Cooper wrote:
>> On 23/10/2025 9:57 am, Anthony PERARD wrote:
>>> From: Anthony PERARD<anthony.perard@vates.tech>
>>>
>>> If not available, fallback to using YAJL.
>>>
>>> The code is using json_c_visit() which was introduced in 0.13.
>>> json_object_new_null() and json_object_new_uint64() where added to
>>> 0.14. And the last one json_object_new_array_ext() was introduced in
>>> 0.15.
>>>
>>> Signed-off-by: Anthony PERARD<anthony.perard@vates.tech>
>> Acked-by: Andrew Cooper<andrew.cooper3@citrix.com>
>>
>> However, you should adjust README and possibly Changelog.md to give this
>> new minimum version.
>
> Will this do?
>
> diff --git a/CHANGELOG.md b/CHANGELOG.md
> index 0cf9ad2d95..fc4f6d7c8a 100644
> --- a/CHANGELOG.md
> +++ b/CHANGELOG.md
> @@ -14,8 +14,8 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/)
> - Debian Trixie added to CI. Debian Bullseye retired from CI for RISC-V due
> to the baseline change.
> - Linux based device model stubdomains are now fully supported.
> - - New dependency on library json-c, the toolstack will prefer it to `YAJL`
> - when available.
> + - New dependency on library json-c 0.15 or later, the toolstack will prefer it
> + to `YAJL` when available.
>
> - On x86:
> - Restrict the cache flushing done as a result of guest physical memory map
> diff --git a/README b/README
> index eaee78bd73..53a4d5c2ae 100644
> --- a/README
> +++ b/README
> @@ -53,7 +53,8 @@ provided by your OS distributor:
> * Development install of Python 2.7 or later (e.g., python-dev)
> * Development install of curses (e.g., libncurses-dev)
> * Development install of uuid (e.g. uuid-dev)
> - * Development install of json-c (e.g. libjson-c-dev) or yajl (e.g. libyajl-dev)
> + * Development install of json-c 0.15 or later (e.g. libjson-c-dev)
> + or yajl (e.g. libyajl-dev)
> * Development install of libaio (e.g. libaio-dev) version 0.3.107 or
> greater.
> * Development install of GLib v2.0 (e.g. libglib2.0-dev)
>
> Cheers,
LGTM. Free to add my:
Acked-by: Oleksii Kurochko<oleksii.kurochko@gmail.com>
~ Oleksii
>
[-- Attachment #2: Type: text/html, Size: 3331 bytes --]
next prev parent reply other threads:[~2025-10-23 15:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-23 8:57 [XEN PATCH for-4.21] tools: require at least json-c 0.15 Anthony PERARD
2025-10-23 9:41 ` Jan Beulich
2025-10-23 14:44 ` Oleksii Kurochko
2025-10-23 14:45 ` Andrew Cooper
2025-10-23 15:04 ` Anthony PERARD
2025-10-23 15:05 ` Andrew Cooper
2025-10-23 15:22 ` Oleksii Kurochko [this message]
2025-10-24 19:03 ` Jason Andryuk
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=d9924b94-36d0-4d7e-9a9b-bd4ea38f538d@gmail.com \
--to=oleksii.kurochko@gmail.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=anthony@xenproject.org \
--cc=jbeulich@suse.com \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).