mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "tip-bot2 for Alexey Makhalov" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: kernel test robot <lkp@intel.com>,
	Alexey Makhalov <alexey.makhalov@broadcom.com>,
	"Borislav Petkov (AMD)" <bp@alien8.de>,
	x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: x86/urgent] drm/vmwgfx: Fix missing HYPERVISOR_GUEST dependency
Date: Wed, 19 Jun 2024 09:55:24 -0000	[thread overview]
Message-ID: <171879092484.10875.16127804390885200858.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20240616012511.198243-1-alexey.makhalov@broadcom.com>

The following commit has been merged into the x86/urgent branch of tip:

Commit-ID:     8c4d6945fe5bd04ff847c3c788abd34ca354ecee
Gitweb:        https://git.kernel.org/tip/8c4d6945fe5bd04ff847c3c788abd34ca354ecee
Author:        Alexey Makhalov <alexey.makhalov@broadcom.com>
AuthorDate:    Sat, 15 Jun 2024 18:25:10 -07:00
Committer:     Borislav Petkov (AMD) <bp@alien8.de>
CommitterDate: Mon, 17 Jun 2024 11:56:54 +02:00

drm/vmwgfx: Fix missing HYPERVISOR_GUEST dependency

VMWARE_HYPERCALL alternative will not work as intended without VMware guest code
initialization.

  [ bp: note that this doesn't reproduce with newer gccs so it must be
    something gcc-9-specific. ]

Closes: https://lore.kernel.org/oe-kbuild-all/202406152104.FxakP1MB-lkp@intel.com/
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: Alexey Makhalov <alexey.makhalov@broadcom.com>
Signed-off-by: Borislav Petkov (AMD) <bp@alien8.de>
Link: https://lore.kernel.org/r/20240616012511.198243-1-alexey.makhalov@broadcom.com
---
 drivers/gpu/drm/vmwgfx/Kconfig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/gpu/drm/vmwgfx/Kconfig b/drivers/gpu/drm/vmwgfx/Kconfig
index faddae3..6f1ac94 100644
--- a/drivers/gpu/drm/vmwgfx/Kconfig
+++ b/drivers/gpu/drm/vmwgfx/Kconfig
@@ -2,7 +2,7 @@
 config DRM_VMWGFX
 	tristate "DRM driver for VMware Virtual GPU"
 	depends on DRM && PCI && MMU
-	depends on X86 || ARM64
+	depends on (X86 && HYPERVISOR_GUEST) || ARM64
 	select DRM_TTM
 	select DRM_TTM_HELPER
 	select MAPPING_DIRTY_HELPERS

      parent reply	other threads:[~2024-06-19 10:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-15 13:22 [tip:x86/vmware 4/8] vmwgfx_msg.c:undefined reference to `vmware_hypercall_slow' kernel test robot
2024-06-15 14:33 ` Borislav Petkov
2024-06-15 20:41   ` Alexey Makhalov
2024-06-15 21:41   ` Alexey Makhalov
2024-06-16  1:25 ` [PATCH 1/2] drm/vmwgfx: Fix missing HYPERVISOR_GUEST dependency Alexey Makhalov
2024-06-16  1:25   ` [PATCH 2/2] iio: dac: Fix dependencies of AD9739A Alexey Makhalov
2024-06-17  9:04     ` Borislav Petkov
2024-06-17 20:48       ` Alexey Makhalov
2024-06-17 21:02         ` Borislav Petkov
2024-06-17  9:07   ` [PATCH 1/2] drm/vmwgfx: Fix missing HYPERVISOR_GUEST dependency Borislav Petkov
2024-06-17 10:01     ` Borislav Petkov
2024-06-17 13:47       ` Zack Rusin
2024-06-17 20:51     ` Alexey Makhalov
2024-06-17 21:17       ` Borislav Petkov
2024-06-17 22:48         ` Alexey Makhalov
2024-06-19  9:55   ` tip-bot2 for Alexey Makhalov [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=171879092484.10875.16127804390885200858.tip-bot2@tip-bot2 \
    --to=tip-bot2@linutronix.de \
    --cc=alexey.makhalov@broadcom.com \
    --cc=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=x86@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

all inboxes | Powered by JetHome®