From: James Zhu <jamesz@amd.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Alex Deucher <alexdeucher@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
DRI <dri-devel@lists.freedesktop.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Alex Deucher <alexander.deucher@amd.com>,
Dave Airlie <airlied@redhat.com>, James Zhu <James.Zhu@amd.com>
Subject: Re: linux-next: build failure after merge of the amdgpu tree
Date: Thu, 18 May 2023 23:10:32 -0400 [thread overview]
Message-ID: <c4768d59-8247-e94b-fdc9-46801beeba07@amd.com> (raw)
In-Reply-To: <20230519100608.7e836126@canb.auug.org.au>
Hi Stephen,
I saw
https://gitlab.freedesktop.org/agd5f/linux/-/blob/amd-staging-drm-next/drivers/gpu/drm/amd/amdgpu/amdgpu_ctx.c#349
should not have this error.
Thanks!
James Zhu
On 2023-05-18 20:06, Stephen Rothwell wrote:
> Hi all,
>
> After merging the amdgpu tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/gpu/drm/amd/amdgpu/amdgpu_ctx.c: In function 'amdgpu_ctx_init':
> drivers/gpu/drm/amd/amdgpu/amdgpu_ctx.c:348:26: error: 'fpriv' undeclared (first use in this function)
> 348 | ctx->ctx_mgr = &(fpriv->ctx_mgr);
> | ^~~~~
>
> Caused by commit
>
> 2458393a4e98 ("drm/amdgpu: keep amdgpu_ctx_mgr in ctx structure")
>
> I have used the amdgpu tree from next-20230518 for today.
>
next prev parent reply other threads:[~2023-05-19 3:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 0:06 linux-next: build failure after merge of the amdgpu tree Stephen Rothwell
2023-05-19 3:10 ` James Zhu [this message]
2023-05-19 13:38 ` Alex Deucher
-- strict thread matches above, loose matches on Subject: below --
2024-08-19 1:56 Stephen Rothwell
[not found] <20231010124357.5251e100@canb.auug.org.au>
2023-10-19 1:06 ` Stephen Rothwell
2023-10-24 0:59 ` Stephen Rothwell
2023-10-24 12:57 ` Alex Deucher
2023-10-24 19:52 ` Alex Deucher
2023-10-24 21:47 ` Stephen Rothwell
[not found] <20220307111342.105ce204@canb.auug.org.au>
[not found] ` <YiYC2fQgf7d/QPSM@sirena.org.uk>
2022-03-08 11:15 ` Noralf Trønnes
2021-12-03 1:11 Stephen Rothwell
2021-09-17 0:57 Stephen Rothwell
2021-07-28 12:34 Mark Brown
2021-02-05 2:12 Stephen Rothwell
[not found] <20200612102552.2d573ebb@canb.auug.org.au>
2020-06-26 1:47 ` Stephen Rothwell
[not found] <20190626212212.25b41df4@canb.auug.org.au>
2019-06-27 3:35 ` Stephen Rothwell
2019-06-27 14:18 ` Alex Deucher
2019-06-27 22:01 ` Stephen Rothwell
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=c4768d59-8247-e94b-fdc9-46801beeba07@amd.com \
--to=jamesz@amd.com \
--cc=James.Zhu@amd.com \
--cc=airlied@redhat.com \
--cc=alexander.deucher@amd.com \
--cc=alexdeucher@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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