public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Atul Kumar Pant <atulpant.linux@gmail.com>
To: paul@paul-moore.com, eparis@redhat.com
Cc: Atul Kumar Pant <atulpant.linux@gmail.com>,
	audit@vger.kernel.org, linux-kernel@vger.kernel.org,
	shuah@kernel.org
Subject: [PATCH v1] kernel: Moves trailing statements to next line
Date: Wed, 16 Aug 2023 02:17:51 +0530	[thread overview]
Message-ID: <20230815204751.52481-1-atulpant.linux@gmail.com> (raw)

Fixes following checkpatch.pl issue:
ERROR: trailing statements should be on next line

Signed-off-by: Atul Kumar Pant <atulpant.linux@gmail.com>
---
 kernel/audit.c       | 3 ++-
 kernel/auditfilter.c | 3 ++-
 2 files changed, 4 insertions(+), 2 deletions(-)

diff --git a/kernel/audit.c b/kernel/audit.c
index 9bc0b0301198..a5393eda7f9d 100644
--- a/kernel/audit.c
+++ b/kernel/audit.c
@@ -323,7 +323,8 @@ static inline int audit_rate_check(void)
 	unsigned long		now;
 	int			retval	   = 0;
 
-	if (!audit_rate_limit) return 1;
+	if (!audit_rate_limit)
+		return 1;
 
 	spin_lock_irqsave(&lock, flags);
 	if (++messages < audit_rate_limit) {
diff --git a/kernel/auditfilter.c b/kernel/auditfilter.c
index 42d99896e7a6..a25757f09255 100644
--- a/kernel/auditfilter.c
+++ b/kernel/auditfilter.c
@@ -694,7 +694,8 @@ static struct audit_rule_data *audit_krule_to_data(struct audit_krule *krule)
 			data->values[i] = f->val;
 		}
 	}
-	for (i = 0; i < AUDIT_BITMASK_SIZE; i++) data->mask[i] = krule->mask[i];
+	for (i = 0; i < AUDIT_BITMASK_SIZE; i++)
+		data->mask[i] = krule->mask[i];
 
 	return data;
 }
-- 
2.25.1


             reply	other threads:[~2023-08-15 20:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-15 20:47 Atul Kumar Pant [this message]
2023-08-15 22:16 ` [PATCH v1] kernel: Moves trailing statements to next line Paul Moore

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=20230815204751.52481-1-atulpant.linux@gmail.com \
    --to=atulpant.linux@gmail.com \
    --cc=audit@vger.kernel.org \
    --cc=eparis@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul@paul-moore.com \
    --cc=shuah@kernel.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