linux-kernel - Re: linux-next: build warning after merge of the drm 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: <413ff283-4341-532b-7815-43956805526d@intel.com>
Date:   Mon, 7 Nov 2022 12:31:11 -0800
From:   John Harrison <john.c.harrison@...el.com>
To:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Dave Airlie <airlied@...hat.com>,
        DRI <dri-devel@...ts.freedesktop.org>
CC:     Umesh Nerlige Ramappa <umesh.nerlige.ramappa@...el.com>,
        "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 tree

On 11/6/2022 19:29, Stephen Rothwell wrote:
> Hi all,
>
> After merging the drm tree, today's linux-next build (KCONFIG_NAME)
> produced this warning:
>
> drivers/gpu/drm/i915/i915_perf_types.h:319: warning: Function parameter or member 'lock' not described in 'i915_perf_stream'
>
> Introduced by commit
>
>    2db609c01495 ("drm/i915/perf: Replace gt->perf.lock with stream->lock for file ops")
>
Yes, a fix has been posted - 
https://patchwork.freedesktop.org/series/110633/

It is unclear how this escaped. It wasn't spotted in code review but 
moreover, the CI pre-merge doc build returned clean for that patch set 
(https://patchwork.freedesktop.org/series/107584/).

John.