RE: [PATCH] x86: Use printk_once() instead of opencoding it

> From: Andrew Cooper > Sent: Thursday, May 11, 2023 3:34 AM > > Technically our helper post-dates all of these examples, but it's good cleanup > nevertheless. None of these examples should be using fully locked > test_and_set_bool() in the first place. > > No functional change. > > Signed-off

Re: [PATCH] x86: Use printk_once() instead of opencoding it

On 10.05.2023 21:33, Andrew Cooper wrote: > Technically our helper post-dates all of these examples, but it's good cleanup > nevertheless. None of these examples should be using fully locked > test_and_set_bool() in the first place. > > No functional change. > > Signed-off-by: Andrew Cooper Re

[PATCH] x86: Use printk_once() instead of opencoding it

Technically our helper post-dates all of these examples, but it's good cleanup nevertheless. None of these examples should be using fully locked test_and_set_bool() in the first place. No functional change. Signed-off-by: Andrew Cooper --- CC: Jan Beulich CC: Roger Pau Monné CC: Wei Liu CC: