From: hanyu001@208suo.com
To: linux@armlinux.org.uk
Cc: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: nwfpe: add require space after that ','
Date: Fri, 21 Jul 2023 16:03:27 +0800 [thread overview]
Message-ID: <5c05ddf2c6e0e1a8ba90fadf0d3fd957@208suo.com> (raw)
In-Reply-To: <tencent_4488AA292A6FC649887668C96A0DCF050509@qq.com>
Fix below checkpatch errors:
./arch/arm/nwfpe/double_cpdo.c:56: ERROR: space required after that ','
(ctx:VxV)
./arch/arm/nwfpe/double_cpdo.c:61: ERROR: space required after that ','
(ctx:VxV)
./arch/arm/nwfpe/double_cpdo.c:75: ERROR: space required after that ','
(ctx:VxV)
Signed-off-by: Yu Han <hanyu001@208suo.com>
---
arch/arm/nwfpe/double_cpdo.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/arm/nwfpe/double_cpdo.c b/arch/arm/nwfpe/double_cpdo.c
index 344bb7c46176..e8b56ab0262e 100644
--- a/arch/arm/nwfpe/double_cpdo.c
+++ b/arch/arm/nwfpe/double_cpdo.c
@@ -53,12 +53,12 @@ static float64 (*const dyadic_double[16])(struct
roundingData*, float64 rFn, flo
[FRD_CODE >> 20] = float64_rdv,
};
-static float64 float64_mvf(struct roundingData *roundData,float64 rFm)
+static float64 float64_mvf(struct roundingData *roundData, float64 rFm)
{
return rFm;
}
-static float64 float64_mnf(struct roundingData *roundData,float64 rFm)
+static float64 float64_mnf(struct roundingData *roundData, float64 rFm)
{
union float64_components u;
@@ -72,7 +72,7 @@ static float64 float64_mnf(struct roundingData
*roundData,float64 rFm)
return u.f64;
}
-static float64 float64_abs(struct roundingData *roundData,float64 rFm)
+static float64 float64_abs(struct roundingData *roundData, float64 rFm)
{
union float64_components u;
parent reply other threads:[~2023-07-21 8:03 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <tencent_4488AA292A6FC649887668C96A0DCF050509@qq.com>]
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=5c05ddf2c6e0e1a8ba90fadf0d3fd957@208suo.com \
--to=hanyu001@208suo.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
/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
all inboxes | Powered by JetHome®