Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Manszewski, Christoph" <christoph.manszewski@intel.com>
To: Jagmeet Randhawa <jagmeet.randhawa@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH v3] lib/gpgpu_fill: Add support for Xe2 platforms
Date: Mon, 6 Nov 2023 12:55:56 +0100	[thread overview]
Message-ID: <3e414bbd-78bf-420e-8217-778db7105c69@intel.com> (raw)
In-Reply-To: <20231103204719.690769-1-jagmeet.randhawa@intel.com>

Hi Jagmeet,

On 3.11.2023 21:47, Jagmeet Randhawa wrote:
> Addressing Christoph Manszewskis comments: Added brackets to remaining else if
> statements, and fixed the XE2 format issue. I ran checkpatch and
> everything seems good, there was trailing white space errors but those I

$ curl -s 
https://patchwork.freedesktop.org/api/1.0/series/125979/revisions/1/mbox/ 
 > a.patch
$ ./scripts/checkpatch.pl a.patch
WARNING: Prefer a maximum 75 chars per line (possible unwrapped commit 
description?)
#21:
iga64 -p=2 -Wall -Xprint-ldst -Xauto-deps --assemble xe2lpg_gpgpu_kernel.asm

ERROR: space required before the open brace '{'
#99: FILE: lib/gpu_cmds.c:331:
+	if (intel_graphics_ver(devid) >= IP_VER(20, 0)){

WARNING: Block comments should align the * on each line
#101: FILE: lib/gpu_cmds.c:333:
+		/*
+		* Up until now, SURFACEFORMAT_R8_UNROM was used regardless of the 
'bpp' value.

ERROR: space required before the open brace '{'
#122: FILE: lib/gpu_cmds.c:354:
+	else if (intel_graphics_ver(devid) >= IP_VER(12, 50)){

ERROR: else should follow close brace '}'
#122: FILE: lib/gpu_cmds.c:354:
+	}
+	else if (intel_graphics_ver(devid) >= IP_VER(12, 50)){

ERROR: space required before the open brace '{'
#127: FILE: lib/gpu_cmds.c:358:
+	else if (intel_graphics_ver(devid) >= IP_VER(9, 0)){

ERROR: else should follow close brace '}'
#127: FILE: lib/gpu_cmds.c:358:
+	}
+	else if (intel_graphics_ver(devid) >= IP_VER(9, 0)){

ERROR: space required before the open brace '{'
#132: FILE: lib/gpu_cmds.c:362:
+	else if (intel_graphics_ver(devid) >= IP_VER(8, 0)){

ERROR: else should follow close brace '}'
#132: FILE: lib/gpu_cmds.c:362:
+	}
+	else if (intel_graphics_ver(devid) >= IP_VER(8, 0)){

ERROR: else should follow close brace '}'
#137: FILE: lib/gpu_cmds.c:366:
+	}
+	else {

WARNING: Missing a blank line after declarations
#150: FILE: lib/gpu_cmds.c:990:
+	uint32_t dword_length = intel_graphics_ver(ibb->devid) >= IP_VER(20, 0);
+	intel_bb_out(ibb, XEHP_STATE_COMPUTE_MODE | dword_length);

ERROR: trailing whitespace
#212: FILE: lib/gpu_cmds.c:1131:
+^I$

WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
#223:
new file mode 100644

ERROR: code indent should use tabs where possible
#251: FILE: lib/intel_batchbuffer.c:759:
+                fill = xe2lpg_gpgpu_fillfunc;$

WARNING: please, no spaces at the start of a line
#251: FILE: lib/intel_batchbuffer.c:759:
+                fill = xe2lpg_gpgpu_fillfunc;$

Apart from the 'MAINTAINERS' file warning and maybe commit msg line 
lenght, all other warnings *and especially errors* are easily fixable 
and have to be fixed.

Thanks,
Christoph

> believe are false positives and are inconsistent with the rest of the
> code styling therefore I ignored them
> 
> Addresing Kamil Koniecznys comments: I fixed the header, and added
> Dominiks r-b
> 
> Jagmeet Randhawa (1):
>    lib/gpgpu_fill: Add support for Xe2 platforms
> 
>   lib/gpgpu_fill.c                              | 23 +++++++
>   lib/gpgpu_fill.h                              |  6 ++
>   lib/gpu_cmds.c                                | 61 ++++++++++++++++---
>   .../shaders/gpgpu/xe2lpg_gpgpu_kernel.asm     | 13 ++++
>   lib/intel_batchbuffer.c                       |  4 +-
>   5 files changed, 96 insertions(+), 11 deletions(-)
>   create mode 100644 lib/i915/shaders/gpgpu/xe2lpg_gpgpu_kernel.asm
> 

      parent reply	other threads:[~2023-11-06 11:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-03 20:47 [igt-dev] [PATCH v3] lib/gpgpu_fill: Add support for Xe2 platforms Jagmeet Randhawa
2023-11-03 20:47 ` [igt-dev] [PATCH 1/1] " Jagmeet Randhawa
2023-11-06 12:03   ` Manszewski, Christoph
2023-11-03 21:56 ` [igt-dev] ✓ CI.xeBAT: success for series starting with [1/1] " Patchwork
2023-11-03 22:01 ` [igt-dev] ✓ Fi.CI.BAT: " Patchwork
2023-11-04 14:47 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2023-11-06 11:55 ` Manszewski, Christoph [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=3e414bbd-78bf-420e-8217-778db7105c69@intel.com \
    --to=christoph.manszewski@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=jagmeet.randhawa@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