From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 87C2DC77B75 for ; Mon, 8 May 2023 07:51:15 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229616AbjEHHvO (ORCPT ); Mon, 8 May 2023 03:51:14 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57646 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233588AbjEHHvL (ORCPT ); Mon, 8 May 2023 03:51:11 -0400 Received: from casper.infradead.org (casper.infradead.org [IPv6:2001:8b0:10b:1236::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 59A2D1AED1; Mon, 8 May 2023 00:51:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=casper.20170209; h=In-Reply-To:Content-Transfer-Encoding: Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date: Sender:Reply-To:Content-ID:Content-Description; bh=LefI14uzybxKQyNSLakt+X2OjjVEG+ovmxbHqRlX8zg=; b=YkxCYdQtSBIxc8X95awBBkGzJR hjAEsP2lFevrFz43FVIJeiFvcNrwXOVoYw+fKbUToGW275kozsh+E/y0okukvvvlG0CzYQmFov9JU zC9niGRmCNpT+K5n1DVwnKRRkY5bTx0dNIlNEfhdRQLJIQpvvcDhG9qBsn5KnK3HDSCQxQFvbWONX SdK5I3XQviqU3GCbv1kdgJHs1BEDXKYG6ci5YHeyQPpmXMpfn7LXeV7TyXzD7/YRq9YtrA3P7ew1v lyHreVA3Sau3uia3UTiXU5FVkjnQrbh8REdIXkUAgSh0aIdKanL2LMT/SFw2FE4f+wYw4ri9Govj2 U8rMwi3g==; Received: from j130084.upc-j.chello.nl ([24.132.130.84] helo=noisy.programming.kicks-ass.net) by casper.infradead.org with esmtpsa (Exim 4.94.2 #2 (Red Hat Linux)) id 1pvve5-00DwqU-B3; Mon, 08 May 2023 07:50:57 +0000 Received: by noisy.programming.kicks-ass.net (Postfix, from userid 1000) id 08941302188; Mon, 8 May 2023 09:50:56 +0200 (CEST) Date: Mon, 8 May 2023 09:50:55 +0200 From: Peter Zijlstra To: Randy Dunlap Cc: Stephen Rothwell , Mathieu Desnoyers , Linux Kernel Mailing List , Linux Next Mailing List Subject: Re: linux-next: build warnings after merge of Linus' tree Message-ID: <20230508075055.GA12756@noisy.programming.kicks-ass.net> References: <20230508144947.3ac1dfe9@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-next@vger.kernel.org On Sun, May 07, 2023 at 09:52:22PM -0700, Randy Dunlap wrote: >=20 >=20 > On 5/7/23 21:49, Stephen Rothwell wrote: > > Hi all, > >=20 > > While building Linus' tree, today's linux-next build (htmldocs) > > produced these warnings: > >=20 > > kernel/sched/core.c:11496: warning: Cannot understand * @cid_lock: Gua= rantee forward-progress of cid allocation. > > on line 11496 - I thought it was a doc line > > kernel/sched/core.c:11505: warning: Cannot understand * @use_cid_lock:= Select cid allocation behavior: lock-free vs spinlock. > > on line 11505 - I thought it was a doc line > >=20 > > Introduced by commit > >=20 > > 223baf9d17f2 ("sched: Fix performance regression introduced by mm_cid= ") > >=20 >=20 > I have sent a patch: > https://lore.kernel.org/lkml/20230428031111.322-1-rdunlap@infradead.org > but haven't seen any replies to it (possibly due to the merge window or t= ravel). I have it, and now that -rc1 is out the door, I'll queue it for -urgent.