From: "Michael S. Tsirkin" <mst@redhat.com>
To: BALATON Zoltan <balaton@eik.bme.hu>
Cc: Max Filippov <jcmvbkbc@gmail.com>,
Damien Zammit <damien@zamaudio.com>,
qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH qemu] timer/i8254: Fix one shot PIT mode
Date: Sun, 26 Feb 2023 08:03:47 -0500 [thread overview]
Message-ID: <20230226080328-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <59513eba-4cd3-2e0f-c81a-fac19407cb3d@eik.bme.hu>
On Sun, Feb 26, 2023 at 01:11:19PM +0100, BALATON Zoltan wrote:
> On Sun, 26 Feb 2023, Max Filippov wrote:
> > On Sun, Feb 26, 2023 at 1:18 AM Damien Zammit <damien@zamaudio.com> wrote:
> > >
> > > Hi Michael,
> > >
> > > Thanks for reviewing this on a weekend!
> > >
> > > On 26/2/23 19:51, Michael S. Tsirkin wrote:
> > > > On Sun, Feb 26, 2023 at 01:58:10AM +0000, Damien Zammit wrote:
> > > > > case 0:
> > > > > - out = (d >= s->count);
> > > > > - break;
> > > >
> > > >
> > > > I think you need something like
> > > > /* FALLTHRU */
> > > > here otherwise some gcc versions will warn.
> > > >
> > > > > case 1:
> > > > > - out = (d < s->count);
> > > > > + out = (d >= s->count);
> > >
> > > It seems that there are quite a number of these consecutive fallthrough cases
> > > without /* FALLTHRU */ in i8254_common.c
> > >
> > > Can these be fixed in a separate patch?
> >
> > I believe that the comment is only needed when there's code
> > between the labels and is not needed between the labels that
> > follow each other.
>
> I think so too, I have some of these consecutive case labels in my code and
> never had a problem with that. Only when you have a statement between labels
> without break is when a comment is needed.
>
> Regards,
> BALATON Zoltan
I just tried and it looks like you are right. Pls ignore sorry about the
noise.
--
MST
next prev parent reply other threads:[~2023-02-26 13:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-26 1:58 [PATCH qemu] timer/i8254: Fix one shot PIT mode Damien Zammit
2023-02-26 8:51 ` Michael S. Tsirkin
2023-02-26 9:17 ` Damien Zammit
2023-02-26 9:45 ` Max Filippov
2023-02-26 12:11 ` BALATON Zoltan
2023-02-26 13:03 ` Michael S. Tsirkin [this message]
2023-05-15 16:15 ` Michael Tokarev
-- strict thread matches above, loose matches on Subject: below --
2023-10-06 2:36 Damien Zammit
2023-10-06 5:19 ` Michael S. Tsirkin
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=20230226080328-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=balaton@eik.bme.hu \
--cc=damien@zamaudio.com \
--cc=jcmvbkbc@gmail.com \
--cc=pbonzini@redhat.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.