Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18;
Sender: Ingo Molnar <mingo.kernel.org@gmail.com>
Date:   Thu, 24 Mar 2022 09:40:24 +0100
From:   Ingo Molnar <mingo@kernel.org>
To:     Linus Torvalds <torvalds@linux-foundation.org>
Cc:     Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Peter Zijlstra <peterz@infradead.org>,
        Will Deacon <will@kernel.org>,
        Waiman Long <longman@redhat.com>,
        Boqun Feng <boqun.feng@gmail.com>,
        Thomas Gleixner <tglx@linutronix.de>,
        Borislav Petkov <bp@alien8.de>,
        Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] locking changes for v5.18
Message-ID: <YjwueBQoung7rFD+@gmail.com>
References: <YjhdcJB4FaLfsoyO@gmail.com>
 <CAHk-=wjS6ptr5=JqmmyEb_qTjDz_68+S=h1o1bL1fEyArVOymA@mail.gmail.com>
 <CAHk-=whNBs07foho7=QxVbs_hnpDfPP3s2fwyXK-reNw67mU=g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAHk-=whNBs07foho7=QxVbs_hnpDfPP3s2fwyXK-reNw67mU=g@mail.gmail.com>
Precedence: bulk


* Linus Torvalds <torvalds@linux-foundation.org> wrote:

> On Tue, Mar 22, 2022 at 3:05 PM Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> >
> > I see that the -mm tree has a fix for this,[..]
> 
> Ok, usually I strive to let the patch-bomb from Andrew sit in a branch
> of its own for a while (in case somebody replies to one of Andrew's
> emails I can then fix things up).
> 
> But I decided to just apply and merge the series immediately instead,
> partly to just have this issue sorted out.
> 
> Let's hope there's nothing dodgy in there..

Thanks!

> > I thought -tip had started checking with clang, but apparently not.

Only intermittently on my side - it only recently started working reliably 
& it doubles the not inconsiderable test time :-/

> > I see that the -mm tree has a fix for this, but I'm rather unhappy that 
> > the -tip tree build checking has deteriorated so much, and clang builds 
> > will now have a pointless build error that will cause issues for 
> > bisect.

Will try to add better clang testing, seems to have better warnings in a 
couple of areas.

Thanks,

	Ingo