[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e45299d9-379e-4f28-bfdf-82927d78a15e@sirena.org.uk>
Date: Fri, 28 Jun 2024 19:06:09 +0100
From: Mark Brown <broonie@...nel.org>
To: Michal Wajdeczko <michal.wajdeczko@...el.com>
Cc: 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>,
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 Fri, Jun 28, 2024 at 07:58:23PM +0200, Michal Wajdeczko wrote:
> On 28.06.2024 19:03, Mark Brown wrote:
> > /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
> > 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]
The fixup claims that it was a bogus merge in drm-tip rather than the
commit above which introduced the function.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists