Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Auld <matthew.auld@intel.com>
To: Maarten Lankhorst <dev@lankhorst.se>, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH] drm/xe: Fxi typo in Kconfig
Date: Fri, 27 Jun 2025 09:39:44 +0100	[thread overview]
Message-ID: <8b8f41a4-779d-4b6c-ae5f-ad780474577f@intel.com> (raw)
In-Reply-To: <20250627074119.347826-1-dev@lankhorst.se>

On 27/06/2025 08:41, Maarten Lankhorst wrote:
> doubut -> doubt.
> 
> Signed-off-by: Maarten Lankhorst <dev@lankhorst.se>

In the commit title also s/Fxi/Fix :)

Reviewed-by: Matthew Auld <matthew.auld@intel.com>

> ---
>   drivers/gpu/drm/xe/Kconfig | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/gpu/drm/xe/Kconfig b/drivers/gpu/drm/xe/Kconfig
> index 553c29e1030b1..4048a781323b6 100644
> --- a/drivers/gpu/drm/xe/Kconfig
> +++ b/drivers/gpu/drm/xe/Kconfig
> @@ -85,7 +85,7 @@ config DRM_XE_GPUSVM
>   	  Enable this option if you want support for CPU to GPU address
>   	  mirroring.
>   
> -	  If in doubut say "Y".
> +	  If in doubt say "Y".
>   
>   config DRM_XE_PAGEMAP
>   	bool "Enable device memory pool for SVM"
> @@ -96,7 +96,7 @@ config DRM_XE_PAGEMAP
>   	  Disable this option only if you don't want to expose local device
>   	  memory for SVM. Will reduce KMD memory footprint when disabled.
>   
> -	  If in doubut say "Y".
> +	  If in doubt say "Y".
>   
>   config DRM_XE_FORCE_PROBE
>   	string "Force probe xe for selected Intel hardware IDs"


  reply	other threads:[~2025-06-27  8:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-27  7:41 [PATCH] drm/xe: Fxi typo in Kconfig Maarten Lankhorst
2025-06-27  8:39 ` Matthew Auld [this message]
2025-07-01 15:05   ` Lucas De Marchi
2025-06-30 12:18 ` ✓ CI.KUnit: success for " Patchwork
2025-06-30 12:56 ` ✓ Xe.CI.BAT: " Patchwork
2025-07-01 12:51 ` ✗ Xe.CI.Full: failure " Patchwork

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=8b8f41a4-779d-4b6c-ae5f-ad780474577f@intel.com \
    --to=matthew.auld@intel.com \
    --cc=dev@lankhorst.se \
    --cc=intel-xe@lists.freedesktop.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