dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Dave Airlie <airlied@linux.ie>, DRI <dri-devel@lists.freedesktop.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the amdgpu tree
Date: Thu, 21 Jan 2021 11:53:41 +1100	[thread overview]
Message-ID: <20210121115341.012c1a55@canb.auug.org.au> (raw)
In-Reply-To: <20210120171501.61aa0786@canb.auug.org.au>


[-- Attachment #1.1: Type: text/plain, Size: 863 bytes --]

Hi all,

On Wed, 20 Jan 2021 17:15:01 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> On Fri, 15 Jan 2021 12:00:14 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > 
> > After merging the amdgpu tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> > 
> > drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c: In function 'dm_set_vblank':
> > drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:5380:33: warning: unused variable 'dm' [-Wunused-variable]
> >  5380 |  struct amdgpu_display_manager *dm = &adev->dm;
> >       |                                 ^~
> > 
> > Caused by commit
> > 
> >   98ab5f3513f9 ("drm/amd/display: Fix deadlock during gpu reset v3")  
> 
> I am still getting this warning.

I now get this warning from the drm tree merge.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

       reply	other threads:[~2021-01-21  0:53 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210115120014.4211dec6@canb.auug.org.au>
     [not found] ` <20210120171501.61aa0786@canb.auug.org.au>
2021-01-21  0:53   ` Stephen Rothwell [this message]
2021-01-21  3:07     ` linux-next: build warning after merge of the amdgpu tree Alex Deucher
2021-01-21  8:32       ` Daniel Vetter
2024-01-30  2:56 Stephen Rothwell
2024-04-21 23:56 ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2024-01-30  2:54 Stephen Rothwell
2024-04-21 23:54 ` Stephen Rothwell
     [not found] <20230815210747.6c409362@canb.auug.org.au>
2023-08-16  1:57 ` Stephen Rothwell
     [not found] <20221026121428.5181969a@canb.auug.org.au>
2023-07-11 23:12 ` Stephen Rothwell
2023-06-09  4:02 Stephen Rothwell
2023-06-07  2:45 Stephen Rothwell
     [not found] <20210416124044.53d4beee@canb.auug.org.au>
2021-04-21  6:40 ` Stephen Rothwell
2021-04-23 20:36   ` Alex Deucher
2021-04-23 22:39     ` Stephen Rothwell
     [not found] <20210322170014.3e022928@canb.auug.org.au>
2021-04-21  6:15 ` Stephen Rothwell
     [not found] <20210311220033.7c5fe548@canb.auug.org.au>
2021-04-21  6:10 ` Stephen Rothwell
     [not found] <20201117154514.2c378d99@canb.auug.org.au>
2020-12-14 19:56 ` Stephen Rothwell
2020-12-15  2:49   ` Stephen Rothwell
2019-12-18 23:18 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=20210121115341.012c1a55@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=Bhawanpreet.Lakha@amd.com \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    /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).