[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAHk-=whb9BT4OkPUM4UkOCVKB28Oi6JC5sXey=FnvNN37aX0eQ@mail.gmail.com>
Date: Mon, 13 Jan 2025 08:18:45 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Guenter Roeck <linux@...ck-us.net>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Fabio Estevam <festevam@...x.de>,
Linus Walleij <linus.walleij@...aro.org>, Waiman Long <longman@...hat.com>
Subject: Re: Linux 6.13-rc4
On Mon, 13 Jan 2025 at 02:40, Peter Zijlstra <peterz@...radead.org> wrote:
>
> If Linus wants it now, I suppose I can send him a pull for it, but
> otherwise, it'll got in during the merge window, which is soon upon us
> anyway.
I think it's fine. It's a bit annoying to have these tests show
failures, but at the same time this is pretty much a "debug option for
an odd architecture".
It's not like anybody is seriously using PROVE_RAW_LOCK_NESTING on
sparc64 and being held up by this, and as you say, we'll get it fixed
soon enough.
That said, in general I'd just like known testing issues to be fixed
sooner rather than later, just so that the _testing_ is easier (and so
that it doesn't end up accumulating).
And I appreciate Guenter testing the odd cases that generally
otherwise would fall between the cracks.
Linus
Powered by blists - more mailing lists