From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Dave Airlie <airlied@redhat.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: "Mark Brown" <broonie@kernel.org>,
DRI <dri-devel@lists.freedesktop.org>,
"Piotr Piórkowski" <piotr.piorkowski@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: Thu, 04 Jul 2024 09:02:21 +0200 [thread overview]
Message-ID: <8de22d252014aa52e631eb1bcf8e85d50e96c29e.camel@linux.intel.com> (raw)
In-Reply-To: <10c3d9b8-bf5b-42c1-9c87-36828f5c995c@intel.com>
Hi
On Wed, 2024-07-03 at 13:46 +0200, Michal Wajdeczko wrote:
> + Rodrigo for help
>
> On 03.07.2024 04:36, Stephen Rothwell wrote:
> > 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:2
> > > 7: 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.
> >
I see that git for an unknown reason introduces this line as an
automatic resolve merging drm-next into the drm-tip build. Later there
was a manual fixup for this after merging another branch into drm-tip
but that's too late.
So I've added a manual fixup to drm-rerere to remove this line just
after the merge that somehow introduces it.
/Thomas
prev parent reply other threads:[~2024-07-04 7:02 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
2024-07-03 11:46 ` Michal Wajdeczko
2024-07-04 7:02 ` Thomas Hellström [this message]
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=8de22d252014aa52e631eb1bcf8e85d50e96c29e.camel@linux.intel.com \
--to=thomas.hellstrom@linux.intel.com \
--cc=airlied@redhat.com \
--cc=broonie@kernel.org \
--cc=buildfailureaftermergeofthedrmtree@sirena.org.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=michal.wajdeczko@intel.com \
--cc=piotr.piorkowski@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).