From: Matthew Brost <matthew.brost@intel.com>
To: Francois Dugast <francois.dugast@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH] fixup! drm/xe: Add min/max cap for engine scheduler properties
Date: Mon, 21 Aug 2023 18:18:07 +0000 [thread overview]
Message-ID: <ZOOqXw17PwaP2tgz@DUT025-TGLU.fm.intel.com> (raw)
In-Reply-To: <20230821135347.7-1-francois.dugast@intel.com>
On Mon, Aug 21, 2023 at 01:53:47PM +0000, Francois Dugast wrote:
> Fix typos in options descriptions.
>
> Signed-off-by: Francois Dugast <francois.dugast@intel.com>
Reviewed-by: Matthew Brost <matthew.brost@intel.com>
> ---
> drivers/gpu/drm/xe/Kconfig.profile | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/Kconfig.profile b/drivers/gpu/drm/xe/Kconfig.profile
> index 4bc080547d5f..ba17a25e8db3 100644
> --- a/drivers/gpu/drm/xe/Kconfig.profile
> +++ b/drivers/gpu/drm/xe/Kconfig.profile
> @@ -5,7 +5,7 @@ config DRM_XE_JOB_TIMEOUT_MAX
> Configures the default max job timeout after which job will
> be forcefully taken away from scheduler.
> config DRM_XE_JOB_TIMEOUT_MIN
> - int "Default max job timeout (ms)"
> + int "Default min job timeout (ms)"
> default 1 # milliseconds
> help
> Configures the default min job timeout after which job will
> @@ -31,14 +31,14 @@ config DRM_XE_PREEMPT_TIMEOUT
> an arbitration point and yield to HW before the timer expires, the
> HW will be reset to allow the more important context to execute.
> config DRM_XE_PREEMPT_TIMEOUT_MAX
> - int "Default max preempt timeout (us)"
> + int "Default max preempt timeout (us)"
> default 10000000 # microseconds
> help
> Configures the default max preempt timeout after which context
> will be forcefully taken away and higher priority context will
> run.
> config DRM_XE_PREEMPT_TIMEOUT_MIN
> - int "Default min preempt timeout (us)"
> + int "Default min preempt timeout (us)"
> default 1 # microseconds
> help
> Configures the default min preempt timeout after which context
> --
> 2.34.1
>
next prev parent reply other threads:[~2023-08-21 18:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-21 13:53 [Intel-xe] [PATCH] fixup! drm/xe: Add min/max cap for engine scheduler properties Francois Dugast
2023-08-21 18:18 ` Matthew Brost [this message]
2023-08-22 12:07 ` [Intel-xe] ✓ CI.Patch_applied: success for " Patchwork
2023-08-22 12:07 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-08-22 12:09 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-08-22 12:12 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-08-22 12:13 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-08-22 12:13 ` [Intel-xe] ✗ CI.checksparse: warning " Patchwork
2023-08-22 12:39 ` [Intel-xe] ✓ CI.BAT: success " 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=ZOOqXw17PwaP2tgz@DUT025-TGLU.fm.intel.com \
--to=matthew.brost@intel.com \
--cc=francois.dugast@intel.com \
--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