[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <712046ed-2481-4644-80d7-707bbe8b5c20@intel.com>
Date: Fri, 28 Jun 2024 19:58:23 +0200
From: Michal Wajdeczko <michal.wajdeczko@...el.com>
To: Mark Brown <broonie@...nel.org>, Dave Airlie <airlied@...hat.com>,
DRI <dri-devel@...ts.freedesktop.org>,
Piotr PiĆ³rkowski <piotr.piorkowski@...el.com>,
Rodrigo Vivi <rodrigo.vivi@...el.com>,
Lucas De Marchi <lucas.demarchi@...el.com>
Cc: buildfailureaftermergeofthedrmtree@...ena.org.uk,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the drm
On 28.06.2024 19:03, Mark Brown wrote:
> Hi all,
>
> After merging the drm tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> /tmp/next/build/drivers/gpu/drm/xe/xe_gt_sriov_pf_config.c: In function 'pf_get_threshold':
> /tmp/next/build/drivers/gpu/drm/xe/xe_gt_sriov_pf_config.c:1788:27: error: unused variable 'xe' [-Werror=unused-variable]
> 1788 | struct xe_device *xe = gt_to_xe(gt);
> | ^~
> cc1: all warnings being treated as errors
>
> Caused by commit
>
> 629df234bfe73d ("drm/xe/pf: Introduce functions to configure VF thresholds")
it must have been something else wrong, as this commit [1] does not
contain this line, it was not part of patch itself [2] and I can't find
any other commit related to this function on drm-tip
but it was noticed today and some fixup was already applied [3]
[1]
https://gitlab.freedesktop.org/drm/xe/kernel/-/commit/629df234bfe73dacb4bb0daa4bc2c14824dba159
[2] https://patchwork.freedesktop.org/patch/594015/?series=133236&rev=2
[3]
https://patchwork.freedesktop.org/patch/601248/?series=135512&rev=1#comment_1094525
>
> I have used the tree from 20240627 instead.
Powered by blists - more mailing lists