linux-kernel - Re: linux-next: build warning after merge of the drm-misc tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <2a9db303-a06e-d266-0d04-f6f6aaa6d2c4@amd.com>
Date:   Mon, 28 Mar 2022 09:26:35 -0400
From:   Andrey Grodzovsky <andrey.grodzovsky@....com>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Daniel Vetter <daniel.vetter@...ll.ch>,
        Intel Graphics <intel-gfx@...ts.freedesktop.org>,
        DRI <dri-devel@...ts.freedesktop.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build warning after merge of the drm-misc tree


On 2022-03-27 19:56, Stephen Rothwell wrote:
> Hi Andrey,
>
> On Tue, 1 Mar 2022 22:26:12 -0500 Andrey Grodzovsky <andrey.grodzovsky@....com> wrote:
>> On 2022-03-01 20:31, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> On Thu, 20 Jan 2022 14:26:39 +1100 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>>>> On Wed, 17 Nov 2021 13:49:26 +1100 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>>>>> After merging the drm-misc tree, today's linux-next build (htmldocs)
>>>>> produced this warning:
>>>>>
>>>>> include/drm/gpu_scheduler.h:316: warning: Function parameter or member 'work' not described in 'drm_sched_job'
>>>>>
>>>>> Introduced by commit
>>>>>
>>>>>     542cff7893a3 ("drm/sched: Avoid lockdep spalt on killing a processes")
>>>> I am still seeing this warning.
>>> I am still seeing this warning.
>>>   
>> Please check you have commit c7703ce38c1e Andrey Grodzovsky   3 weeks ago    drm/amdgpu: Fix htmldoc warning
> I do have commit c7703ce38c1e (in fact it is in Linus' tree), but that
> commit does not address the warning above.  I am still (as of Friday)
> getting that warning.


Got it, i was confused. Sent a patch to fix, please RB.

Andrey