From: Peter Zijlstra <peterz@infradead.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warnings after merge of Linus' tree
Date: Mon, 8 May 2023 09:50:55 +0200 [thread overview]
Message-ID: <20230508075055.GA12756@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <cccc2dc5-b4d5-3b2b-bd23-b63c20b1023a@infradead.org>
On Sun, May 07, 2023 at 09:52:22PM -0700, Randy Dunlap wrote:
>
>
> On 5/7/23 21:49, Stephen Rothwell wrote:
> > Hi all,
> >
> > While building Linus' tree, today's linux-next build (htmldocs)
> > produced these warnings:
> >
> > kernel/sched/core.c:11496: warning: Cannot understand * @cid_lock: Guarantee 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
> >
> > Introduced by commit
> >
> > 223baf9d17f2 ("sched: Fix performance regression introduced by mm_cid")
> >
>
> 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 travel).
I have it, and now that -rc1 is out the door, I'll queue it for -urgent.
next prev parent reply other threads:[~2023-05-08 7:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 4:49 linux-next: build warnings after merge of Linus' tree Stephen Rothwell
2023-05-08 4:52 ` Randy Dunlap
2023-05-08 4:53 ` Randy Dunlap
2023-05-08 7:50 ` Peter Zijlstra [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-11-13 1:55 Stephen Rothwell
2025-11-13 8:16 ` Mauro Carvalho Chehab
2025-11-13 16:23 ` Jonathan Corbet
2025-11-13 22:01 ` Mauro Carvalho Chehab
2025-11-13 22:28 ` Randy Dunlap
2025-11-13 22:42 ` Randy Dunlap
2025-11-13 8:49 ` Michael S. Tsirkin
2025-11-13 10:32 ` Mauro Carvalho Chehab
2025-04-07 8:59 Venkat
2025-04-07 9:47 ` Venkat Rao Bagalkote
2025-04-06 22:48 Stephen Rothwell
2021-03-29 9:04 Stephen Rothwell
2021-04-21 6:23 ` Stephen Rothwell
2021-04-21 13:06 ` Rob Herring
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230508075055.GA12756@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.