From: Thomas Monjalon <thomas@monjalon.net>
To: Jan Blunck <jblunck@infradead.org>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] crypto/scheduler: fix build
Date: Sun, 09 Jul 2017 15:26:00 +0200 [thread overview]
Message-ID: <2291044.izmqMtvmdQ@xps> (raw)
In-Reply-To: <CALe+Z02_taVy7kyeWax_Yj3VXLAo1ooq8nP7TT8Tb64iPMLceQ@mail.gmail.com>
09/07/2017 12:43, Jan Blunck:
> On Sun, Jul 9, 2017 at 6:38 AM, Thomas Monjalon <thomas@monjalon.net> wrote:
> > 09/07/2017 11:44, Jan Blunck:
> >> Fixes 4c07e0552f0a ("crypto/scheduler: add multicore scheduling mode")
> >>
> >> drivers/crypto/scheduler/scheduler_multicore.c: In function 'scheduler_stop':
> >> drivers/crypto/scheduler/scheduler_multicore.c:286:2: error: 'for' loop
> >> initial declarations are only allowed in C99 or C11 mode
> >> for (uint16_t i = 0; i < sched_ctx->nb_wc; i++)
> >> ^
> >
> > I wonder why I have not spotted it.
> > What is your compiler? which version?
>
> This is with Debian Jessie:
>
> gcc version 4.9.2 (Debian 4.9.2-10)
OK, so I could update the title to "fix build with old gcc" ?
And add in the log that it has been seen with gcc 4.9.2.
Do you agree?
PS: I am testing with gcc 7.1.
next prev parent reply other threads:[~2017-07-09 13:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-09 9:44 Jan Blunck
2017-07-09 10:38 ` Thomas Monjalon
2017-07-09 10:43 ` Jan Blunck
2017-07-09 13:26 ` Thomas Monjalon [this message]
2017-07-09 15:05 ` Thomas Monjalon
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=2291044.izmqMtvmdQ@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=jblunck@infradead.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 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).