rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Hubbard <jhubbard@nvidia.com>
To: Danilo Krummrich <dakr@kernel.org>,
	aliceryhl@google.com, acourbot@nvidia.com
Cc: nouveau@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	rust-for-linux@vger.kernel.org
Subject: Re: [PATCH 1/2] drm: nova: depend on CONFIG_64BIT
Date: Tue, 28 Oct 2025 12:37:55 -0700	[thread overview]
Message-ID: <2a080bb7-7c61-4fd0-9d5f-495afdbebfe9@nvidia.com> (raw)
In-Reply-To: <20251028110058.340320-1-dakr@kernel.org>

On 10/28/25 4:00 AM, Danilo Krummrich wrote:
> nova-core already depends on CONFIG_64BIT, hence also depend on
> CONFIG_64BIT for nova-drm.
> 
> Signed-off-by: Danilo Krummrich <dakr@kernel.org>
> ---
>  drivers/gpu/drm/nova/Kconfig | 1 +
>  1 file changed, 1 insertion(+)

Reviewed-by: John Hubbard <jhubbard@nvidia.com>

thanks,
John Hubbard

> 
> diff --git a/drivers/gpu/drm/nova/Kconfig b/drivers/gpu/drm/nova/Kconfig
> index cca6a3fea879..2a70aac64d7e 100644
> --- a/drivers/gpu/drm/nova/Kconfig
> +++ b/drivers/gpu/drm/nova/Kconfig
> @@ -1,5 +1,6 @@
>  config DRM_NOVA
>  	tristate "Nova DRM driver"
> +	depends on 64BIT
>  	depends on DRM=y
>  	depends on PCI
>  	depends on RUST


      parent reply	other threads:[~2025-10-28 19:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-28 11:00 [PATCH 1/2] drm: nova: depend on CONFIG_64BIT Danilo Krummrich
2025-10-28 11:00 ` [PATCH 2/2] drm: nova: select NOVA_CORE Danilo Krummrich
2025-10-28 11:42   ` Alexandre Courbot
2025-10-28 19:33   ` John Hubbard
2025-10-30 22:21   ` Timur Tabi
2025-10-30 22:24     ` John Hubbard
2025-10-28 11:42 ` [PATCH 1/2] drm: nova: depend on CONFIG_64BIT Alexandre Courbot
2025-10-28 19:37 ` John Hubbard [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=2a080bb7-7c61-4fd0-9d5f-495afdbebfe9@nvidia.com \
    --to=jhubbard@nvidia.com \
    --cc=acourbot@nvidia.com \
    --cc=aliceryhl@google.com \
    --cc=dakr@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=nouveau@lists.freedesktop.org \
    --cc=rust-for-linux@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).