Re: [PATCH printk v1] printk: ringbuffer: Add KUnit test

On Thu 2024-11-21 15:56:34, John Ogness wrote: > From: Thomas Weißschuh > > The KUnit test validates the correct operation of the ringbuffer. > A separate dedicated ringbuffer is used so that the global printk > ringbuffer is not touched. Thanks a lot for upstreaming this test! > --- a/init/Kco

Re: [PATCH printk v1] printk: ringbuffer: Add KUnit test

Hi John, kernel test robot noticed the following build errors: [auto build test ERROR on rust/rust-next] [also build test ERROR on linus/master v6.12 next-20241122] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as doc

Re: [PATCH printk v1] printk: ringbuffer: Add KUnit test

Hi David, On 2024-11-22, David Gow wrote: > It's a little unusual for a KUnit test -- particularly since it is > time-based and uses lots of threads. This isn't a problem, but it's > definitely a good thing that it's marked as slow. Additionally, KUnit > doesn't track any extra threads spawned, s

Re: [PATCH printk v1] printk: ringbuffer: Add KUnit test

On Thu, 21 Nov 2024 at 22:50, John Ogness wrote: > > From: Thomas Weißschuh > > The KUnit test validates the correct operation of the ringbuffer. > A separate dedicated ringbuffer is used so that the global printk > ringbuffer is not touched. > > Co-developed-by: John Ogness > Signed-off-by: Joh