linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: Huang Rui <ray.huang@amd.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build warning after merge of the amdgpu tree
Date: Mon, 18 Jan 2021 16:29:19 +1100	[thread overview]
Message-ID: <20210118162919.51f2dd3a@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 515 bytes --]

Hi all,

After merging the amdgpu tree, today's linux-next build (powerpc
allyesconfig) gave this warning:

drivers/gpu/drm/amd/amdgpu/../pm/swsmu/smu11/vangogh_ppt.c: In function 'vangogh_init_smc_tables':
drivers/gpu/drm/amd/amdgpu/../pm/swsmu/smu11/vangogh_ppt.c:338:5: warning: "CONFIG_X86" is not defined, evaluates to 0 [-Wundef]
  338 | #if CONFIG_X86
      |     ^~~~~~~~~~

Caused by commit

  9dd19d5232a6 ("drm/amdgpu: fix build error without x86 kconfig")

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2021-01-18  5:30 UTC|newest]

Thread overview: 83+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-18  5:29 Stephen Rothwell [this message]
2021-01-18  5:56 ` linux-next: build warning after merge of the amdgpu tree Huang, Ray
2021-01-18  6:52   ` Stephen Rothwell
2021-01-18 12:35     ` Huang Rui
  -- strict thread matches above, loose matches on Subject: below --
2024-01-30  2:56 Stephen Rothwell
2024-01-30  2:54 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 20:45 ` Alex Deucher
2023-06-09  4:02 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
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-23 20:36   ` Alex Deucher
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-03-11 11:00 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-15  1:00 Stephen Rothwell
2021-01-20  6:15 ` Stephen Rothwell
2021-01-21  0:53   ` Stephen Rothwell
2021-01-21  3:07     ` Alex Deucher
2021-01-21  8:32       ` Daniel Vetter
2020-11-17  4:45 Stephen Rothwell
2020-12-14 19:56 ` 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-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=20210118162919.51f2dd3a@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=alexdeucher@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=ray.huang@amd.com \
    /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).