From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: Martin Wilck <Martin.Wilck@suse.com>,
"bmarzins@redhat.com" <bmarzins@redhat.com>,
"christophe.varoqui@opensvc.com" <christophe.varoqui@opensvc.com>
Cc: "mail@eworm.de" <mail@eworm.de>,
"dm-devel@redhat.com" <dm-devel@redhat.com>,
"besser82@fedoraproject.org" <besser82@fedoraproject.org>,
Eric Haszlakiewicz <erh+git@nimenees.com>
Subject: Re: [PATCH 1/1] libdmmp: Add support for upcoming json-c 0.14.0.
Date: Fri, 29 May 2020 13:45:09 +0200 [thread overview]
Message-ID: <42eef647-d9ef-7956-5852-27188bc4665f@gmail.com> (raw)
In-Reply-To: <d092428a245e0b5d88b70f03a473d7df7b95cd27.camel@suse.com>
On 5/29/20 11:12 AM, Martin Wilck wrote:
> On Thu, 2020-05-28 at 23:10 -0500, Benjamin Marzinski wrote:
>> From: Björn Esser <besser82@fedoraproject.org>
>>
>> TRUE/FALSE are not defined anymore. 1 and 0 are used instead.
>> This is backwards compatible, as earlier versions of json-c are
>> using the same integer values in their present definitions.
>>
>> Signed-off-by: Benjamin Marzinski <bmarzins@redhat.com>
>> ---
>> libdmmp/libdmmp_private.h | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/libdmmp/libdmmp_private.h b/libdmmp/libdmmp_private.h
>> index ac85b63f..4378962b 100644
>> --- a/libdmmp/libdmmp_private.h
>> +++ b/libdmmp/libdmmp_private.h
>> @@ -82,7 +82,7 @@ static out_type func_name(struct dmmp_context *ctx,
>> const char *var_name) { \
>> do { \
>> json_type j_type = json_type_null; \
>> json_object *j_obj_tmp = NULL; \
>> - if (json_object_object_get_ex(j_obj, key, &j_obj_tmp) != TRUE)
>> { \
>> + if (json_object_object_get_ex(j_obj, key, &j_obj_tmp) != 1) { \
>> _error(ctx, "Invalid JSON output from multipathd IPC: "
>> \
>> "key '%s' not found", key); \
>> rc = DMMP_ERR_IPC_ERROR; \
>
> Did you see
> https://www.redhat.com/archives/dm-devel/2020-May/msg00261.html ?
>
> This has first been reported to the list by Christian (
> https://www.redhat.com/archives/dm-devel/2020-April/msg00261.html), and
> brought to my attention later by Xose. I personally thought the change
> from boolean to int is a step in the wrong direction, therefore I
> submitted my modified version using stdboolh. If everyone else is fine
> with the int, it's not worth arguing about it.
>
> Regards,
> Martin
>
> PS: Can anyone explain why json-c did this? Looks like a "cause hassle
> for downstream devs and users for no good reason" kind of thing to
> me...
>
Add Eric Haszlakiewicz to CC.
Done at: https://github.com/json-c/json-c/commit/0992aac61f8b087efd7094e9ac2b84fa9c040fcd
next prev parent reply other threads:[~2020-05-29 11:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 4:10 [PATCH 0/1] multipath: libdmmp json fix Benjamin Marzinski
2020-05-29 4:10 ` [PATCH 1/1] libdmmp: Add support for upcoming json-c 0.14.0 Benjamin Marzinski
2020-05-29 9:12 ` Martin Wilck
2020-05-29 11:45 ` Xose Vazquez Perez [this message]
2020-05-30 14:25 ` Eric Hawicz
2020-05-29 16:19 ` Benjamin Marzinski
2020-05-29 16:26 ` Martin Wilck
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=42eef647-d9ef-7956-5852-27188bc4665f@gmail.com \
--to=xose.vazquez@gmail.com \
--cc=Martin.Wilck@suse.com \
--cc=besser82@fedoraproject.org \
--cc=bmarzins@redhat.com \
--cc=christophe.varoqui@opensvc.com \
--cc=dm-devel@redhat.com \
--cc=erh+git@nimenees.com \
--cc=mail@eworm.de \
/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.