All of lore.kernel.org
 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: Alex Deucher <alexdeucher@gmail.com>,
	Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@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: 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 #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

WARNING: multiple messages have this Message-ID (diff)
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  5:56 UTC|newest]

Thread overview: 147+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-15  1:00 linux-next: build warning after merge of the amdgpu tree Stephen Rothwell
2021-01-20  6:15 ` Stephen Rothwell
2021-01-21  0:53   ` Stephen Rothwell [this message]
2021-01-21  0:53     ` Stephen Rothwell
2021-01-21  3:07     ` Alex Deucher
2021-01-21  3:07       ` Alex Deucher
2021-01-21  8:32       ` Daniel Vetter
2021-01-21  8:32         ` Daniel Vetter
  -- strict thread matches above, loose matches on Subject: below --
2025-11-19  2:22 Stephen Rothwell
2025-12-16  1:07 ` Stephen Rothwell
2025-08-05  3:11 Stephen Rothwell
2025-08-05 14:11 ` Aurabindo Pillai
2025-07-16 10:28 Stephen Rothwell
2025-07-16 18:45 ` Zhu, Yihan
2025-07-16 19:08   ` Alex Deucher
2025-07-16 19:24     ` Zhu, Yihan
2025-07-16 19:40       ` Alex Hung
2025-07-17  2:15       ` Randy Dunlap
2025-08-01  4:45 ` Stephen Rothwell
2025-06-19 10:59 Stephen Rothwell
2025-06-04  3:23 Stephen Rothwell
2025-06-04 13:31 ` Zhu, Yihan
2025-05-09  8:58 Stephen Rothwell
2025-04-22 10:33 Stephen Rothwell
2025-06-03 22:57 ` Stephen Rothwell
2025-04-22 10:29 Stephen Rothwell
2025-04-09  3:10 Stephen Rothwell
2025-04-10  4:40 ` Stephen Rothwell
2025-04-10 19:11   ` Li, Roman
2025-03-19  9:34 Stephen Rothwell
2025-03-19  9:38 ` Kaszewski, Dominik
2025-03-19 11:00   ` Stephen Rothwell
2025-03-19 11:13     ` Kaszewski, Dominik
2025-04-03  6:01   ` Stephen Rothwell
2025-04-03  6:08     ` Kaszewski, Dominik
2025-02-26  4:44 Stephen Rothwell
2025-01-17  5:45 Stephen Rothwell
2025-01-13  4:54 Stephen Rothwell
2025-01-16  6:08 ` Stephen Rothwell
2024-10-02  4:17 Stephen Rothwell
2024-08-26  5:59 Stephen Rothwell
2024-09-06  8:46 ` Stephen Rothwell
2024-05-31  5:26 Stephen Rothwell
2024-07-14 23:07 ` Stephen Rothwell
2024-05-14  7:14 Stephen Rothwell
2024-05-14 18:20 ` Nirujogi, Pratap
2024-05-14 19:07   ` Alex Deucher
2024-05-14  7:11 Stephen Rothwell
2024-07-14 23:04 ` Stephen Rothwell
2024-05-01  5:19 Stephen Rothwell
2024-07-14 23:02 ` Stephen Rothwell
2024-01-30  2:56 Stephen Rothwell
2024-01-30  2:56 ` Stephen Rothwell
2024-04-21 23:56 ` Stephen Rothwell
2024-07-14 22:59   ` Stephen Rothwell
2024-01-30  2:54 Stephen Rothwell
2024-01-30  2:54 ` Stephen Rothwell
2024-04-21 23:54 ` Stephen Rothwell
2024-07-14 22:57   ` Stephen Rothwell
2023-12-14  4:29 Stephen Rothwell
2023-12-12  0:04 Stephen Rothwell
2023-12-12  3:01 ` Stephen Rothwell
2023-12-12  9:01   ` Melissa Wen
2023-12-12 15:05     ` Alex Deucher
2023-10-17  3:35 Stephen Rothwell
2023-09-21  2:31 Stephen Rothwell
2023-08-15 11:07 Stephen Rothwell
2023-08-16  1:57 ` Stephen Rothwell
2023-08-16  1:57   ` Stephen Rothwell
2023-08-16 20:45 ` Alex Deucher
2023-06-09  4:02 Stephen Rothwell
2023-06-09  4:02 ` Stephen Rothwell
2023-06-07  2:45 Stephen Rothwell
2023-06-07  2:45 ` Stephen Rothwell
2023-04-12  4:36 Stephen Rothwell
2023-04-03  7:42 Stephen Rothwell
2023-03-01  0:34 Stephen Rothwell
2023-02-15  4:13 Stephen Rothwell
2023-01-18  3:13 Stephen Rothwell
2022-12-15  0:35 Stephen Rothwell
2022-11-18  6:47 Stephen Rothwell
2022-11-18  8:29 ` Christian König
2022-11-10  7:23 Stephen Rothwell
2022-10-28  3:33 Stephen Rothwell
2022-10-26  1:14 Stephen Rothwell
2023-07-11 23:12 ` Stephen Rothwell
2023-07-11 23:12   ` Stephen Rothwell
2022-10-24  4:14 Stephen Rothwell
2022-08-31  5:37 Stephen Rothwell
2022-10-09 22:58 ` Stephen Rothwell
2022-08-11 22:13 Stephen Rothwell
2022-08-30 23:04 ` Stephen Rothwell
2022-10-05  0:36   ` Stephen Rothwell
2022-08-11  2:05 Stephen Rothwell
2022-08-30  1:48 ` Stephen Rothwell
2022-06-23  7:47 Stephen Rothwell
2022-03-25  8:07 Stephen Rothwell
2022-03-25  8:11 ` Christian König
2021-08-25  2:51 Stephen Rothwell
2021-06-05  2:26 Stephen Rothwell
2021-06-05 14:39 ` Eric Huang
2021-06-03  9:22 Stephen Rothwell
2021-05-28  1:50 Stephen Rothwell
2021-05-04 23:39 Stephen Rothwell
     [not found] ` <DM4PR12MB5133E6A99840D1E8542C0D23F7599@DM4PR12MB5133.namprd12.prod.outlook.com>
2021-05-05  2:55   ` Stephen Rothwell
2021-04-26 12:40 Stephen Rothwell
2021-04-26 14:40 ` Nirmoy
2021-04-16  2:40 Stephen Rothwell
2021-04-16  3:12 ` Liang, Prike
2021-04-16  4:08   ` Stephen Rothwell
2021-04-16  5:47     ` Liang, Prike
2021-04-16  5:51       ` Alex Deucher
2021-04-21  6:40 ` Stephen Rothwell
2021-04-21  6:40   ` Stephen Rothwell
2021-04-23 20:36   ` Alex Deucher
2021-04-23 20:36     ` Alex Deucher
2021-04-23 22:39     ` Stephen Rothwell
2021-04-23 22:39       ` Stephen Rothwell
2021-03-24  6:48 Stephen Rothwell
2021-03-24  2:33 Stephen Rothwell
2021-03-22  6:00 Stephen Rothwell
2021-04-21  6:15 ` Stephen Rothwell
2021-04-21  6:15   ` Stephen Rothwell
2021-03-11 11:00 Stephen Rothwell
2021-04-21  6:10 ` Stephen Rothwell
2021-04-21  6:10   ` Stephen Rothwell
2021-03-09  2:55 Stephen Rothwell
2021-03-03  6:00 Stephen Rothwell
2021-02-23 23:48 Stephen Rothwell
2021-01-18  5:29 Stephen Rothwell
2021-01-18  5:56 ` Huang, Ray
2021-01-18  6:52   ` Stephen Rothwell
2021-01-18 12:35     ` Huang Rui
2020-11-17  4:45 Stephen Rothwell
2020-12-14 19:56 ` Stephen Rothwell
2020-12-14 19:56   ` Stephen Rothwell
2020-12-15  2:49   ` Stephen Rothwell
2020-12-15  2:49     ` Stephen Rothwell
2020-04-23  2:24 Stephen Rothwell
2020-03-13  9:57 Stephen Rothwell
2020-02-04 22:44 Stephen Rothwell
2019-12-18 23:18 Stephen Rothwell
2019-12-18 23:18 ` Stephen Rothwell
2019-11-08  0:21 Stephen Rothwell
2019-07-02  3:53 Stephen Rothwell
2019-05-10  0:59 Stephen Rothwell
2019-05-31  1:27 ` 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=alexdeucher@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.