All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Jafar Abdi" <cafer.abdi@gmail.com>,
	"Daniel P. Berrangé" <berrange@redhat.com>
Subject: [PULL 2/3] authz: fix usage of bool in listfile.c
Date: Fri,  7 Feb 2020 12:24:39 +0000	[thread overview]
Message-ID: <20200207122440.2650229-3-berrange@redhat.com> (raw)
In-Reply-To: <20200207122440.2650229-1-berrange@redhat.com>

From: Jafar Abdi <cafer.abdi@gmail.com>

Clean up wrong usage of FALSE and TRUE in places that use "bool" from stdbool.h.

FALSE and TRUE (with capital letters) are the constants defined by glib for
being used with the "gboolean" type of glib. But some parts of the code also use
TRUE and FALSE for variables that are declared as "bool" (the type from <stdbool.h>).

Signed-off-by: Jafar Abdi <cafer.abdi@gmail.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
---
 authz/listfile.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/authz/listfile.c b/authz/listfile.c
index e7a8c19bcb..b71f57d30a 100644
--- a/authz/listfile.c
+++ b/authz/listfile.c
@@ -239,7 +239,7 @@ qauthz_list_file_init(Object *obj)
 
     authz->file_watch = -1;
 #ifdef CONFIG_INOTIFY1
-    authz->refresh = TRUE;
+    authz->refresh = true;
 #endif
 }
 
-- 
2.24.1



  parent reply	other threads:[~2020-02-07 12:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-07 12:24 [PULL 0/3] Misc patches Daniel P. Berrangé
2020-02-07 12:24 ` [PULL 1/3] io/channel-websock: treat 'binary' and no sub-protocol as the same Daniel P. Berrangé
2020-02-07 12:24 ` Daniel P. Berrangé [this message]
2020-02-07 12:24 ` [PULL 3/3] docs: stop documenting the e1000 NIC model as the default Daniel P. Berrangé
2020-02-07 18:02 ` [PULL 0/3] Misc patches Peter Maydell

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=20200207122440.2650229-3-berrange@redhat.com \
    --to=berrange@redhat.com \
    --cc=cafer.abdi@gmail.com \
    --cc=qemu-devel@nongnu.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 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.