From: Andrew Morton <akpm@linux-foundation.org>
To: James Morse <james.morse@arm.com>
Cc: linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
"Sergei Trofimovich" <slyich@gmail.com>,
matoro <matoro_mailinglist_kernel@matoro.tk>,
"Émeric Maschino" <emeric.maschino@gmail.com>
Subject: Re: [PATCH] ia64: Fix build error due to switch case label appearing next to declaration
Date: Tue, 17 Jan 2023 16:02:03 -0800 [thread overview]
Message-ID: <20230117160203.a1a22c612cdffeeb79b8d397@linux-foundation.org> (raw)
In-Reply-To: <20230117151632.393836-1-james.morse@arm.com>
On Tue, 17 Jan 2023 15:16:32 +0000 James Morse <james.morse@arm.com> wrote:
> Since commit aa06a9bd8533 ("ia64: fix clock_getres(CLOCK_MONOTONIC) to
> report ITC frequency"), gcc 10.1.0 fails to build ia64 with the gnomic:
> | ../arch/ia64/kernel/sys_ia64.c: In function 'ia64_clock_getres':
> | ../arch/ia64/kernel/sys_ia64.c:189:3: error: a label can only be part of a statement and a declaration is not a statement
> | 189 | s64 tick_ns = DIV_ROUND_UP(NSEC_PER_SEC, local_cpu_data->itc_freq);
>
> ...
>
> @@ -185,8 +188,8 @@ ia64_clock_getres(const clockid_t which_clock, struct __kernel_timespec __user *
> switch (which_clock) {
> case CLOCK_REALTIME:
> case CLOCK_MONOTONIC:
> - s64 tick_ns = DIV_ROUND_UP(NSEC_PER_SEC, local_cpu_data->itc_freq);
> - struct timespec64 rtn_tp = ns_to_timespec64(tick_ns);
> + tick_ns = DIV_ROUND_UP(NSEC_PER_SEC, local_cpu_data->itc_freq);
> + rtn_tp = ns_to_timespec64(tick_ns);
> return put_timespec64(&rtn_tp, tp);
> }
>
Huh, how did that sneak through. We usually use an extra set of braces
for this.
Thanks, I'll add cc:stable to this.
prev parent reply other threads:[~2023-01-18 0:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 15:16 [PATCH] ia64: Fix build error due to switch case label appearing next to declaration James Morse
2023-01-17 15:44 ` John Paul Adrian Glaubitz
2023-01-17 19:31 ` Sergei Trofimovich
2023-01-18 11:44 ` James Morse
2023-01-18 0:02 ` Andrew Morton [this message]
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=20230117160203.a1a22c612cdffeeb79b8d397@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=emeric.maschino@gmail.com \
--cc=james.morse@arm.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matoro_mailinglist_kernel@matoro.tk \
--cc=slyich@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