From: "Nilawar, Badal" <badal.nilawar@intel.com>
To: Tejas Upadhyay <tejas.upadhyay@intel.com>,
<intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH] drm/xe/wa: Limit char per line to 100
Date: Fri, 21 Feb 2025 19:23:22 +0530 [thread overview]
Message-ID: <72c23c2a-cb2d-490c-88e3-0cea2799d219@intel.com> (raw)
In-Reply-To: <20250221115344.389975-1-tejas.upadhyay@intel.com>
On 21-02-2025 17:23, Tejas Upadhyay wrote:
> Above 100 char per line checkpatch would complain. Fixing it.
>
> Signed-off-by: Tejas Upadhyay <tejas.upadhyay@intel.com>
> ---
> drivers/gpu/drm/xe/xe_wa.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_wa.c b/drivers/gpu/drm/xe/xe_wa.c
> index 744dba4fdb58..d4982799383c 100644
> --- a/drivers/gpu/drm/xe/xe_wa.c
> +++ b/drivers/gpu/drm/xe/xe_wa.c
> @@ -599,7 +599,8 @@ static const struct xe_rtp_entry_sr engine_was[] = {
> /* Xe3_LPG */
>
> { XE_RTP_NAME("14021402888"),
> - XE_RTP_RULES(GRAPHICS_VERSION_RANGE(3000, 3001), FUNC(xe_rtp_match_first_render_or_compute)),
> + XE_RTP_RULES(GRAPHICS_VERSION_RANGE(3000, 3001),
> + FUNC(xe_rtp_match_first_render_or_compute)),
> XE_RTP_ACTIONS(SET(HALF_SLICE_CHICKEN7, CLEAR_OPTIMIZATION_DISABLE))
> },
> { XE_RTP_NAME("18034896535"),
Reviewed-by: Badal Nilawar <badal.nilawar@intel.com>
Regards,
Badal
next prev parent reply other threads:[~2025-02-21 13:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 11:53 [PATCH] drm/xe/wa: Limit char per line to 100 Tejas Upadhyay
2025-02-21 13:53 ` Nilawar, Badal [this message]
2025-02-21 14:46 ` ✓ CI.Patch_applied: success for " Patchwork
2025-02-21 14:46 ` ✓ CI.checkpatch: " Patchwork
2025-02-21 14:47 ` ✓ CI.KUnit: " Patchwork
2025-02-21 15:04 ` ✓ CI.Build: " Patchwork
2025-02-21 15:06 ` ✓ CI.Hooks: " Patchwork
2025-02-21 15:08 ` ✓ CI.checksparse: " Patchwork
2025-02-21 15:34 ` ✓ Xe.CI.BAT: " Patchwork
2025-02-22 4:43 ` ✗ 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=72c23c2a-cb2d-490c-88e3-0cea2799d219@intel.com \
--to=badal.nilawar@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=tejas.upadhyay@intel.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