public inbox for linux-integrity@vger.kernel.org
 help / color / mirror / Atom feed
From: Chi Wang <wangchi05@163.com>
To: trivial@kernel.org
Cc: Mimi Zohar <zohar@linux.ibm.com>,
	Roberto Sassu <roberto.sassu@huawei.com>,
	Dmitry Kasatkin <dmitry.kasatkin@gmail.com>,
	linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
	Chi Wang <wangchi@kylinos.cn>
Subject: [PATCH] integrity: digsig: Add blank line after declarations
Date: Fri, 27 Feb 2026 14:23:11 +0800	[thread overview]
Message-ID: <20260227062311.140597-1-wangchi05@163.com> (raw)

From: Chi Wang <wangchi@kylinos.cn>

Fixes checkpatch warning:
WARNING: Missing a blank line after declarations
+                       int err = PTR_ERR(keyring[id]);
+                       pr_err("no %s keyring: %d\n", keyring_name[id], err);

Add a blank line after the variable declaration to comply with
the kernel coding style.

Signed-off-by: Chi Wang <wangchi@kylinos.cn>
---
 security/integrity/digsig.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/security/integrity/digsig.c b/security/integrity/digsig.c
index aec350abad86..5e7ba7d3cf99 100644
--- a/security/integrity/digsig.c
+++ b/security/integrity/digsig.c
@@ -49,6 +49,7 @@ static struct key *integrity_keyring_from_id(const unsigned int id)
 			request_key(&key_type_keyring, keyring_name[id], NULL);
 		if (IS_ERR(keyring[id])) {
 			int err = PTR_ERR(keyring[id]);
+
 			pr_err("no %s keyring: %d\n", keyring_name[id], err);
 			keyring[id] = NULL;
 			return ERR_PTR(err);
-- 
2.25.1


             reply	other threads:[~2026-02-27  6:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-27  6:23 Chi Wang [this message]
2026-02-27 18:38 ` [PATCH] integrity: digsig: Add blank line after declarations Mimi Zohar

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=20260227062311.140597-1-wangchi05@163.com \
    --to=wangchi05@163.com \
    --cc=dmitry.kasatkin@gmail.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roberto.sassu@huawei.com \
    --cc=trivial@kernel.org \
    --cc=wangchi@kylinos.cn \
    --cc=zohar@linux.ibm.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