From: Michal Wajdeczko <michal.wajdeczko@intel•com>
To: "Mark Brown" <broonie@kernel•org>,
"Dave Airlie" <airlied@redhat•com>,
DRI <dri-devel@lists•freedesktop.org>,
"Piotr Piórkowski" <piotr.piorkowski@intel•com>,
"Rodrigo Vivi" <rodrigo.vivi@intel•com>,
"Lucas De Marchi" <lucas.demarchi@intel•com>
Cc: buildfailureaftermergeofthedrmtree@sirena•org.uk,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: build failure after merge of the drm
Date: Fri, 28 Jun 2024 19:58:23 +0200 [thread overview]
Message-ID: <712046ed-2481-4644-80d7-707bbe8b5c20@intel.com> (raw)
In-Reply-To: <Zn7s611xnutUFxR0@sirena.org.uk>
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.
next prev parent reply other threads:[~2024-06-28 17:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 17:03 linux-next: build failure after merge of the drm Mark Brown
2024-06-28 17:58 ` Michal Wajdeczko [this message]
2024-06-28 18:06 ` Mark Brown
2024-07-03 2:36 ` Stephen Rothwell
2024-07-03 11:46 ` Michal Wajdeczko
2024-07-04 7:02 ` Thomas Hellström
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=712046ed-2481-4644-80d7-707bbe8b5c20@intel.com \
--to=michal.wajdeczko@intel$(echo .)com \
--cc=airlied@redhat$(echo .)com \
--cc=broonie@kernel$(echo .)org \
--cc=buildfailureaftermergeofthedrmtree@sirena$(echo .)org.uk \
--cc=dri-devel@lists$(echo .)freedesktop.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=lucas.demarchi@intel$(echo .)com \
--cc=piotr.piorkowski@intel$(echo .)com \
--cc=rodrigo.vivi@intel$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox