From: Petr Vorel <pvorel@suse.cz>
To: Richard Palethorpe <rpalethorpe@suse.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 2/6] api/evloop: Add helpers for creating an event loop
Date: Fri, 30 Sep 2022 15:36:07 +0200 [thread overview]
Message-ID: <Yzbwx/JcCtRCfnhI@pevik> (raw)
In-Reply-To: <20220927161408.23743-3-rpalethorpe@suse.com>
Hi Richie,
> +++ b/lib/tst_evloop.c
...
> +void tst_evloop_run(struct tst_evloop *self)
> +{
> + static int saturated_warn;
> + const int maxevents = 128;
> + struct epoll_event events[maxevents];
> +
> + for (;;) {
> + const int ev_num = SAFE_EPOLL_WAIT(self->epollfd, events,
> + maxevents, self->timeout);
> +
> + for (int i = 0; i < ev_num; i++)
I'm sorry we still do not allow to use C99 due CentOS 7 still supported:
lib/tst_evloop.c:80:3: error: 'for' loop initial declarations are only allowed in C99 mode
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-09-30 13:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 16:14 [LTP] [PATCH 0/6] Locally distributed work API Richard Palethorpe via ltp
2022-09-27 16:14 ` [LTP] [PATCH 1/6] api/epoll: Add safe epoll functions Richard Palethorpe via ltp
2022-09-27 16:14 ` [LTP] [PATCH 2/6] api/evloop: Add helpers for creating an event loop Richard Palethorpe via ltp
2022-09-30 13:36 ` Petr Vorel [this message]
2022-09-27 16:14 ` [LTP] [PATCH 3/6] api/state_machine: Add validating state machines Richard Palethorpe via ltp
2022-09-27 16:14 ` [LTP] [PATCH 4/6] api/channel: Add channel abstraction for message passing Richard Palethorpe via ltp
2022-09-30 9:17 ` Petr Vorel
2022-09-27 16:14 ` [LTP] [PATCH 5/6] api/worker: Add library for distributing work over multiple procs Richard Palethorpe via ltp
2022-09-27 16:14 ` [LTP] [PATCH 6/6] read_all: Migrate to the worker lib Richard Palethorpe via ltp
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=Yzbwx/JcCtRCfnhI@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
--cc=rpalethorpe@suse.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.