public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* [PATCH 1/2] arm64: lib: xor-neon: remove redundant filename comment
@ 2026-03-01 15:28 Josh Law
  2026-03-01 15:28 ` [PATCH 2/2] arm64: lib: xor-neon: fix pointer spacing for __restrict Josh Law
  2026-03-02 13:52 ` [PATCH 1/2] arm64: lib: xor-neon: remove redundant filename comment Christoph Hellwig
  0 siblings, 2 replies; 5+ messages in thread
From: Josh Law @ 2026-03-01 15:28 UTC (permalink / raw)
  To: Catalin Marinas, Will Deacon; +Cc: linux-arm-kernel, linux-kernel, Josh Law

The filename in the header comment is redundant and not recommended by Linux kernel coding style.

Signed-off-by: Josh Law <objecting@objecting.org>
---
 arch/arm64/lib/xor-neon.c | 1 -
 1 file changed, 1 deletion(-)

diff --git a/arch/arm64/lib/xor-neon.c b/arch/arm64/lib/xor-neon.c
index 8fffebfa17b2..c65b44a8f134 100644
--- a/arch/arm64/lib/xor-neon.c
+++ b/arch/arm64/lib/xor-neon.c
@@ -1,6 +1,5 @@
 // SPDX-License-Identifier: GPL-2.0-only
 /*
- * arch/arm64/lib/xor-neon.c
  *
  * Authors: Jackie Liu <liuyun01@kylinos.cn>
  * Copyright (C) 2018,Tianjin KYLIN Information Technology Co., Ltd.
-- 
2.43.0


^ permalink raw reply related	[flat|nested] 5+ messages in thread

* [PATCH 2/2] arm64: lib: xor-neon: fix pointer spacing for __restrict
  2026-03-01 15:28 [PATCH 1/2] arm64: lib: xor-neon: remove redundant filename comment Josh Law
@ 2026-03-01 15:28 ` Josh Law
  2026-03-02 13:52 ` [PATCH 1/2] arm64: lib: xor-neon: remove redundant filename comment Christoph Hellwig
  1 sibling, 0 replies; 5+ messages in thread
From: Josh Law @ 2026-03-01 15:28 UTC (permalink / raw)
  To: Catalin Marinas, Will Deacon; +Cc: linux-arm-kernel, linux-kernel, Josh Law

Fix coding style error where 'foo * bar' should be 'foo *bar' for the __restrict qualifier.

Signed-off-by: Josh Law <objecting@objecting.org>
---
 arch/arm64/lib/xor-neon.c | 52 +++++++++++++++++++--------------------
 1 file changed, 26 insertions(+), 26 deletions(-)

diff --git a/arch/arm64/lib/xor-neon.c b/arch/arm64/lib/xor-neon.c
index c65b44a8f134..cdf6ae923e1b 100644
--- a/arch/arm64/lib/xor-neon.c
+++ b/arch/arm64/lib/xor-neon.c
@@ -9,8 +9,8 @@
 #include <linux/module.h>
 #include <asm/neon-intrinsics.h>
 
-static void xor_arm64_neon_2(unsigned long bytes, unsigned long * __restrict p1,
-	const unsigned long * __restrict p2)
+static void xor_arm64_neon_2(unsigned long bytes, unsigned long *__restrict p1,
+	const unsigned long *__restrict p2)
 {
 	uint64_t *dp1 = (uint64_t *)p1;
 	uint64_t *dp2 = (uint64_t *)p2;
@@ -36,9 +36,9 @@ static void xor_arm64_neon_2(unsigned long bytes, unsigned long * __restrict p1,
 	} while (--lines > 0);
 }
 
-static void xor_arm64_neon_3(unsigned long bytes, unsigned long * __restrict p1,
-	const unsigned long * __restrict p2,
-	const unsigned long * __restrict p3)
+static void xor_arm64_neon_3(unsigned long bytes, unsigned long *__restrict p1,
+	const unsigned long *__restrict p2,
+	const unsigned long *__restrict p3)
 {
 	uint64_t *dp1 = (uint64_t *)p1;
 	uint64_t *dp2 = (uint64_t *)p2;
@@ -72,10 +72,10 @@ static void xor_arm64_neon_3(unsigned long bytes, unsigned long * __restrict p1,
 	} while (--lines > 0);
 }
 
-static void xor_arm64_neon_4(unsigned long bytes, unsigned long * __restrict p1,
-	const unsigned long * __restrict p2,
-	const unsigned long * __restrict p3,
-	const unsigned long * __restrict p4)
+static void xor_arm64_neon_4(unsigned long bytes, unsigned long *__restrict p1,
+	const unsigned long *__restrict p2,
+	const unsigned long *__restrict p3,
+	const unsigned long *__restrict p4)
 {
 	uint64_t *dp1 = (uint64_t *)p1;
 	uint64_t *dp2 = (uint64_t *)p2;
@@ -117,11 +117,11 @@ static void xor_arm64_neon_4(unsigned long bytes, unsigned long * __restrict p1,
 	} while (--lines > 0);
 }
 
-static void xor_arm64_neon_5(unsigned long bytes, unsigned long * __restrict p1,
-	const unsigned long * __restrict p2,
-	const unsigned long * __restrict p3,
-	const unsigned long * __restrict p4,
-	const unsigned long * __restrict p5)
+static void xor_arm64_neon_5(unsigned long bytes, unsigned long *__restrict p1,
+	const unsigned long *__restrict p2,
+	const unsigned long *__restrict p3,
+	const unsigned long *__restrict p4,
+	const unsigned long *__restrict p5)
 {
 	uint64_t *dp1 = (uint64_t *)p1;
 	uint64_t *dp2 = (uint64_t *)p2;
@@ -191,9 +191,9 @@ static inline uint64x2_t eor3(uint64x2_t p, uint64x2_t q, uint64x2_t r)
 }
 
 static void xor_arm64_eor3_3(unsigned long bytes,
-	unsigned long * __restrict p1,
-	const unsigned long * __restrict p2,
-	const unsigned long * __restrict p3)
+	unsigned long *__restrict p1,
+	const unsigned long *__restrict p2,
+	const unsigned long *__restrict p3)
 {
 	uint64_t *dp1 = (uint64_t *)p1;
 	uint64_t *dp2 = (uint64_t *)p2;
@@ -226,10 +226,10 @@ static void xor_arm64_eor3_3(unsigned long bytes,
 }
 
 static void xor_arm64_eor3_4(unsigned long bytes,
-	unsigned long * __restrict p1,
-	const unsigned long * __restrict p2,
-	const unsigned long * __restrict p3,
-	const unsigned long * __restrict p4)
+	unsigned long *__restrict p1,
+	const unsigned long *__restrict p2,
+	const unsigned long *__restrict p3,
+	const unsigned long *__restrict p4)
 {
 	uint64_t *dp1 = (uint64_t *)p1;
 	uint64_t *dp2 = (uint64_t *)p2;
@@ -270,11 +270,11 @@ static void xor_arm64_eor3_4(unsigned long bytes,
 }
 
 static void xor_arm64_eor3_5(unsigned long bytes,
-	unsigned long * __restrict p1,
-	const unsigned long * __restrict p2,
-	const unsigned long * __restrict p3,
-	const unsigned long * __restrict p4,
-	const unsigned long * __restrict p5)
+	unsigned long *__restrict p1,
+	const unsigned long *__restrict p2,
+	const unsigned long *__restrict p3,
+	const unsigned long *__restrict p4,
+	const unsigned long *__restrict p5)
 {
 	uint64_t *dp1 = (uint64_t *)p1;
 	uint64_t *dp2 = (uint64_t *)p2;
-- 
2.43.0


^ permalink raw reply related	[flat|nested] 5+ messages in thread

* Re: [PATCH 1/2] arm64: lib: xor-neon: remove redundant filename comment
  2026-03-01 15:28 [PATCH 1/2] arm64: lib: xor-neon: remove redundant filename comment Josh Law
  2026-03-01 15:28 ` [PATCH 2/2] arm64: lib: xor-neon: fix pointer spacing for __restrict Josh Law
@ 2026-03-02 13:52 ` Christoph Hellwig
  2026-03-02 16:01   ` Josh Law
  1 sibling, 1 reply; 5+ messages in thread
From: Christoph Hellwig @ 2026-03-02 13:52 UTC (permalink / raw)
  To: Josh Law
  Cc: Catalin Marinas, Will Deacon, linux-arm-kernel, linux-kernel,
	Josh Law

On Sun, Mar 01, 2026 at 03:28:19PM +0000, Josh Law wrote:
> The filename in the header comment is redundant and not recommended by Linux kernel coding style.

I have a pretty big series pending that changes this file in
meaninful ways.  But even without that please never send standalone
patches for trivial cleanups like this, only do them if you have to
touch the code for another reason anyway.


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [PATCH 1/2] arm64: lib: xor-neon: remove redundant filename comment
  2026-03-02 13:52 ` [PATCH 1/2] arm64: lib: xor-neon: remove redundant filename comment Christoph Hellwig
@ 2026-03-02 16:01   ` Josh Law
  2026-03-03 10:50     ` Catalin Marinas
  0 siblings, 1 reply; 5+ messages in thread
From: Josh Law @ 2026-03-02 16:01 UTC (permalink / raw)
  To: Christoph Hellwig
  Cc: Catalin Marinas, Will Deacon, linux-arm-kernel, linux-kernel,
	Josh Law

2 Mar 2026 13:52:07 Christoph Hellwig <hch@infradead.org>:

> On Sun, Mar 01, 2026 at 03:28:19PM +0000, Josh Law wrote:
>> The filename in the header comment is redundant and not recommended by Linux kernel coding style.
>
> I have a pretty big series pending that changes this file in
> meaninful ways.  But even without that please never send standalone
> patches for trivial cleanups like this, only do them if you have to
> touch the code for another reason anyway.

Hello Cristoph, I am sorry, again
Since I am new to Linux kernel development
I sometimes make mistakes, it's normal.
Patch 2 should be more relevant, all of those I got under checkpatch.pl

V/R
V/R


Josh law

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [PATCH 1/2] arm64: lib: xor-neon: remove redundant filename comment
  2026-03-02 16:01   ` Josh Law
@ 2026-03-03 10:50     ` Catalin Marinas
  0 siblings, 0 replies; 5+ messages in thread
From: Catalin Marinas @ 2026-03-03 10:50 UTC (permalink / raw)
  To: Josh Law
  Cc: Christoph Hellwig, Will Deacon, linux-arm-kernel, linux-kernel,
	Josh Law

On Mon, Mar 02, 2026 at 04:01:45PM +0000, Josh Law wrote:
> 2 Mar 2026 13:52:07 Christoph Hellwig <hch@infradead.org>:
> > On Sun, Mar 01, 2026 at 03:28:19PM +0000, Josh Law wrote:
> >> The filename in the header comment is redundant and not recommended
> >> by Linux kernel coding style.
> >
> > I have a pretty big series pending that changes this file in
> > meaninful ways.  But even without that please never send standalone
> > patches for trivial cleanups like this, only do them if you have to
> > touch the code for another reason anyway.
> 
> Hello Cristoph, I am sorry, again
> Since I am new to Linux kernel development
> I sometimes make mistakes, it's normal.
> Patch 2 should be more relevant, all of those I got under checkpatch.pl

Patch 2 is not relevant either. Unnecessary change that will make things
harder to backport, conflict with other changes.

Please don't run checkpatch.pl on existing code, only on new patches
before they are upstreamed.

-- 
Catalin

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2026-03-03 10:50 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-03-01 15:28 [PATCH 1/2] arm64: lib: xor-neon: remove redundant filename comment Josh Law
2026-03-01 15:28 ` [PATCH 2/2] arm64: lib: xor-neon: fix pointer spacing for __restrict Josh Law
2026-03-02 13:52 ` [PATCH 1/2] arm64: lib: xor-neon: remove redundant filename comment Christoph Hellwig
2026-03-02 16:01   ` Josh Law
2026-03-03 10:50     ` Catalin Marinas

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox