Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tejas Upadhyay <tejas.upadhyay@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: badal.nilawar@intel.com, Tejas Upadhyay <tejas.upadhyay@intel.com>
Subject: [PATCH] drm/xe/wa: Limit char per line to 100
Date: Fri, 21 Feb 2025 17:23:44 +0530	[thread overview]
Message-ID: <20250221115344.389975-1-tejas.upadhyay@intel.com> (raw)

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"),
-- 
2.34.1


             reply	other threads:[~2025-02-21 11:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-21 11:53 Tejas Upadhyay [this message]
2025-02-21 13:53 ` [PATCH] drm/xe/wa: Limit char per line to 100 Nilawar, Badal
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=20250221115344.389975-1-tejas.upadhyay@intel.com \
    --to=tejas.upadhyay@intel.com \
    --cc=badal.nilawar@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