[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87zgv8bdei.fsf@jogness.linutronix.de>
Date: Tue, 29 Jun 2021 22:59:57 +0206
From: John Ogness <john.ogness@...utronix.de>
To: kernel test robot <lkp@...el.com>, Petr Mladek <pmladek@...e.com>
Cc: kbuild-all@...ts.01.org,
Sergey Senozhatsky <senozhatsky@...omium.org>,
Steven Rostedt <rostedt@...dmis.org>,
Thomas Gleixner <tglx@...utronix.de>,
linux-kernel@...r.kernel.org, Petr Mladek <pmladek@...e.com>,
stable@...r.kernel.org
Subject: Re: [PATCH] printk/console: Check consistent sequence number when handling race in console_unlock()
On 2021-06-30, kernel test robot <lkp@...el.com> wrote:
>>> kernel/printk/printk.c:2548:6: warning: variable 'next_seq' set but not used [-Wunused-but-set-variable]
I suppose the correct fix for this warning would be to change the NOP
macros. Currently they are:
#define prb_read_valid(rb, seq, r) false
#define prb_first_valid_seq(rb) 0
They should probably be something like (untested):
#define prb_read_valid(rb, seq, r) \
({ \
(void)(rb); \
(void)(seq); \
(void)(r); \
false; \
})
#define prb_first_valid_seq(rb) \
({ \
(void)(rb); \
0; \
})
John Ogness
Powered by blists - more mailing lists