Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <24a5daa4-2c6c-781d-bbb3-8f5a4f035c08@infradead.org>
Date:   Sun, 7 May 2023 21:53:16 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.10.1
Subject: Re: linux-next: build warnings after merge of Linus' tree
Content-Language: en-US
From:   Randy Dunlap <rdunlap@infradead.org>
To:     Stephen Rothwell <sfr@canb.auug.org.au>,
        Peter Zijlstra <peterz@infradead.org>
Cc:     Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Linux Next Mailing List <linux-next@vger.kernel.org>
References: <20230508144947.3ac1dfe9@canb.auug.org.au>
 <cccc2dc5-b4d5-3b2b-bd23-b63c20b1023a@infradead.org>
In-Reply-To: <cccc2dc5-b4d5-3b2b-bd23-b63c20b1023a@infradead.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: bulk


On 5/7/23 21:52, 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).
> 

Oops, Peter did reply, but no info on merging it.

-- 
~Randy