All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Stefan Berger <stefanb@linux.ibm.com>
Cc: Thomas Huth <thuth@redhat.com>, Jafar Abdi <cafer.abdi@gmail.com>,
	qemu-devel@nongnu.org, QEMU Trivial <qemu-trivial@nongnu.org>,
	stefanha@gmail.com, jusual@mail.ru
Subject: Re: [Qemu-devel] [PATCH V2 4/4] hw/tpm: fix usage of bool in tpm-tis.c
Date: Thu, 7 May 2020 12:52:01 +0100	[thread overview]
Message-ID: <20200507115201.GA1120808@redhat.com> (raw)
In-Reply-To: <471c060c-2abc-50e9-1a51-871ab62185ea@linux.ibm.com>

ping, again, for either qemu-trivial or TPM maintainers to take this
patch.

The other three in this series are merged, but this TPM patch is
still pending.

On Tue, Mar 26, 2019 at 09:55:24AM -0400, Stefan Berger wrote:
> On 3/24/19 3:41 PM, Thomas Huth wrote:
> > 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>
> > > ---
> > >   hw/tpm/tpm_tis.c | 4 ++--
> > >   1 file changed, 2 insertions(+), 2 deletions(-)
> > > 
> > > diff --git a/hw/tpm/tpm_tis.c b/hw/tpm/tpm_tis.c
> > > index fd183e8..c1eb094 100644
> > > --- a/hw/tpm/tpm_tis.c
> > > +++ b/hw/tpm/tpm_tis.c
> > > @@ -611,7 +611,7 @@ static void tpm_tis_mmio_write(void *opaque, hwaddr addr,
> > >               while ((TPM_TIS_IS_VALID_LOCTY(s->active_locty) &&
> > >                       locty > s->active_locty) ||
> > >                       !TPM_TIS_IS_VALID_LOCTY(s->active_locty)) {
> > > -                bool higher_seize = FALSE;
> > > +                bool higher_seize = false;
> > >                   /* already a pending SEIZE ? */
> > >                   if ((s->loc[locty].access & TPM_TIS_ACCESS_SEIZE)) {
> > > @@ -621,7 +621,7 @@ static void tpm_tis_mmio_write(void *opaque, hwaddr addr,
> > >                   /* check for ongoing seize by a higher locality */
> > >                   for (l = locty + 1; l < TPM_TIS_NUM_LOCALITIES; l++) {
> > >                       if ((s->loc[l].access & TPM_TIS_ACCESS_SEIZE)) {
> > > -                        higher_seize = TRUE;
> > > +                        higher_seize = true;
> > >                           break;
> > >                       }
> > >                   }
> > > 
> > Reviewed-by: Thomas Huth <thuth@redhat.com>
> Reviewed-by: Stefan Berger <stefanb@linux.ibm.com>
> > 
> 
> 

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



WARNING: multiple messages have this Message-ID (diff)
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Stefan Berger <stefanb@linux.ibm.com>
Cc: Thomas Huth <thuth@redhat.com>, Jafar Abdi <cafer.abdi@gmail.com>,
	QEMU Trivial <qemu-trivial@nongnu.org>,
	stefanha@gmail.com, qemu-devel@nongnu.org, jusual@mail.ru
Subject: Re: [Qemu-devel] [PATCH V2 4/4] hw/tpm: fix usage of bool in tpm-tis.c
Date: Thu, 7 May 2020 12:52:01 +0100	[thread overview]
Message-ID: <20200507115201.GA1120808@redhat.com> (raw)
In-Reply-To: <471c060c-2abc-50e9-1a51-871ab62185ea@linux.ibm.com>

ping, again, for either qemu-trivial or TPM maintainers to take this
patch.

The other three in this series are merged, but this TPM patch is
still pending.

On Tue, Mar 26, 2019 at 09:55:24AM -0400, Stefan Berger wrote:
> On 3/24/19 3:41 PM, Thomas Huth wrote:
> > 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>
> > > ---
> > >   hw/tpm/tpm_tis.c | 4 ++--
> > >   1 file changed, 2 insertions(+), 2 deletions(-)
> > > 
> > > diff --git a/hw/tpm/tpm_tis.c b/hw/tpm/tpm_tis.c
> > > index fd183e8..c1eb094 100644
> > > --- a/hw/tpm/tpm_tis.c
> > > +++ b/hw/tpm/tpm_tis.c
> > > @@ -611,7 +611,7 @@ static void tpm_tis_mmio_write(void *opaque, hwaddr addr,
> > >               while ((TPM_TIS_IS_VALID_LOCTY(s->active_locty) &&
> > >                       locty > s->active_locty) ||
> > >                       !TPM_TIS_IS_VALID_LOCTY(s->active_locty)) {
> > > -                bool higher_seize = FALSE;
> > > +                bool higher_seize = false;
> > >                   /* already a pending SEIZE ? */
> > >                   if ((s->loc[locty].access & TPM_TIS_ACCESS_SEIZE)) {
> > > @@ -621,7 +621,7 @@ static void tpm_tis_mmio_write(void *opaque, hwaddr addr,
> > >                   /* check for ongoing seize by a higher locality */
> > >                   for (l = locty + 1; l < TPM_TIS_NUM_LOCALITIES; l++) {
> > >                       if ((s->loc[l].access & TPM_TIS_ACCESS_SEIZE)) {
> > > -                        higher_seize = TRUE;
> > > +                        higher_seize = true;
> > >                           break;
> > >                       }
> > >                   }
> > > 
> > Reviewed-by: Thomas Huth <thuth@redhat.com>
> Reviewed-by: Stefan Berger <stefanb@linux.ibm.com>
> > 
> 
> 

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



  reply	other threads:[~2020-05-07 11:52 UTC|newest]

Thread overview: 12+ 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   ` [Qemu-trivial] [Qemu-devel] [PATCH V2 2/4] tests/libqos: fix usage of bool in pci-pc.c Thomas Huth
     [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é [this message]
2020-05-07 11:52         ` Daniel P. Berrangé
2020-05-08 19:42         ` Stefan Berger
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é
2019-09-06 14:36     ` 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=20200507115201.GA1120808@redhat.com \
    --to=berrange@redhat.com \
    --cc=cafer.abdi@gmail.com \
    --cc=jusual@mail.ru \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=stefanb@linux.ibm.com \
    --cc=stefanha@gmail.com \
    --cc=thuth@redhat.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 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.