On 16. 10. 23, 11:12, Florian Eckert wrote:
On 2023-10-16 10:46, m.brock@xxxxxxxxxxxxx wrote:
Florian Eckert wrote on 2023-10-16 09:13:
Has complained about the following construct:
Who is "Has" or who/what has complained?
The test robot who does not agree with my change in the v1 patchset.
Well, you should have put subject to that sentence, so that we can
understand. And not to parse "Has" as a tool/person name ;).
drivers/leds/trigger/ledtrig-tty.c:362:3: error: a label can only be
part of a statement and a declaration is not a statement
Hence move the variable definition to the beginning of the function.
Reported-by: kernel test robot <lkp@xxxxxxxxx>
Closes:
https://lore.kernel.org/oe-kbuild-all/202309270440.IJB24Xap-lkp@xxxxxxxxx/
Signed-off-by: Florian Eckert <fe@xxxxxxxxxx>
---
@@ -124,8 +125,6 @@ static void ledtrig_tty_work(struct work_struct
*work)
if (icount.rx != trigger_data->rx ||
icount.tx != trigger_data->tx) {
- unsigned long interval = LEDTRIG_TTY_INTERVAL;
-
Is this kernel test robot broken?
The test robot does nothing wrong.
I see no label definition here.
case is a label.
And this variable declaration is at the start of a new block which
does not
even require C99 support.
Nah. The block begins after the switch.
So
"""
switch (X) {
type var;
case X:
}
would work. Moving the def after case is no longer at the block beginning.
So just wrap put the case code in a block like we are used to:
"""
case X: {
type var;
}
""".
regards,
--
js
suse labs
