From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Dave Airlie <airlied@redhat•com>
Cc: "Mark Brown" <broonie@kernel•org>,
DRI <dri-devel@lists•freedesktop.org>,
"Piotr Piórkowski" <piotr.piorkowski@intel•com>,
"Michal Wajdeczko" <michal.wajdeczko@intel•com>,
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: Wed, 3 Jul 2024 12:36:43 +1000 [thread overview]
Message-ID: <20240703123643.5b4dc83f@canb.auug.org.au> (raw)
In-Reply-To: <Zn7s611xnutUFxR0@sirena.org.uk>
[-- Attachment #1: Type: text/plain, Size: 789 bytes --]
Hi all,
On Fri, 28 Jun 2024 18:03:39 +0100 Mark Brown <broonie@kernel•org> wrote:
>
> 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")
>
> I have used the tree from 20240627 instead.
I am still seeing that build failure.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-07-03 2:36 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
2024-06-28 18:06 ` Mark Brown
2024-07-03 2:36 ` Stephen Rothwell [this message]
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=20240703123643.5b4dc83f@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--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=michal.wajdeczko@intel$(echo .)com \
--cc=piotr.piorkowski@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