qemu-trivial.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Jafar Abdi <cafer.abdi@gmail.com>, qemu-devel@nongnu.org
Cc: Laurent Vivier <lvivier@redhat.com>,
	stefanha@gmail.com, Paolo Bonzini <pbonzini@redhat.com>,
	jusual@mail.ru, QEMU Trivial <qemu-trivial@nongnu.org>
Subject: Re: [Qemu-trivial] [Qemu-devel] [PATCH V2 2/4] tests/libqos: fix usage of bool in pci-pc.c
Date: Sun, 24 Mar 2019 20:39:32 +0100	[thread overview]
Message-ID: <12da0ce6-9520-0c46-bc65-c8dc361d33bf@redhat.com> (raw)
In-Reply-To: <1553351197-14581-3-git-send-email-cafer.abdi@gmail.com>

On 23/03/2019 15.26, Jafar Abdi wrote:
> 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>
> ---
>  tests/libqos/pci-pc.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/tests/libqos/pci-pc.c b/tests/libqos/pci-pc.c
> index 4ab16fa..407d8af 100644
> --- a/tests/libqos/pci-pc.c
> +++ b/tests/libqos/pci-pc.c
> @@ -125,7 +125,7 @@ void qpci_init_pc(QPCIBusPC *qpci, QTestState *qts, QGuestAllocator *alloc)
>      assert(qts);
>  
>      /* tests can use pci-bus */
> -    qpci->bus.has_buggy_msi = FALSE;
> +    qpci->bus.has_buggy_msi = false;
>  
>      qpci->bus.pio_readb = qpci_pc_pio_readb;
>      qpci->bus.pio_readw = qpci_pc_pio_readw;

Reviewed-by: Thomas Huth <thuth@redhat.com>


  parent reply	other threads:[~2019-03-24 19:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1553351197-14581-1-git-send-email-cafer.abdi@gmail.com>
     [not found] ` <1553351197-14581-2-git-send-email-cafer.abdi@gmail.com>
2019-03-24 19:37   ` [Qemu-trivial] [Qemu-devel] [PATCH V2 1/4] authz: fix usage of bool in listfile.c Thomas Huth
     [not found] ` <1553351197-14581-3-git-send-email-cafer.abdi@gmail.com>
2019-03-24 19:39   ` Thomas Huth [this message]
     [not found] ` <1553351197-14581-4-git-send-email-cafer.abdi@gmail.com>
2019-03-24 19:40   ` [Qemu-trivial] [Qemu-devel] [PATCH V2 3/4] tests/libqos: fix usage of bool in pci-spapr.c Thomas Huth
     [not found] ` <1553351197-14581-5-git-send-email-cafer.abdi@gmail.com>
2019-03-24 19:41   ` [Qemu-trivial] [Qemu-devel] [PATCH V2 4/4] hw/tpm: fix usage of bool in tpm-tis.c Thomas Huth
2019-03-26 13:55     ` Stefan Berger
2020-05-07 11:52       ` Daniel P. Berrangé
2020-05-08 19:42         ` Stefan Berger
2019-03-26  8:18 ` [Qemu-trivial] [PATCH V2 0/4] fix usage of bool Stefan Hajnoczi
2019-09-06 14:36   ` [Qemu-trivial] [Qemu-devel] " Daniel P. Berrangé

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=12da0ce6-9520-0c46-bc65-c8dc361d33bf@redhat.com \
    --to=thuth@redhat.com \
    --cc=cafer.abdi@gmail.com \
    --cc=jusual@mail.ru \
    --cc=lvivier@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=stefanha@gmail.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;
as well as URLs for NNTP newsgroup(s).