From: Mashiro Chen <mashiro.chen@mailbox.org>
To: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com
Cc: netdev@vger.kernel.org, linux-hams@vger.kernel.org,
linux-kernel@vger.kernel.org,
Mashiro Chen <mashiro.chen@mailbox.org>
Subject: [PATCH 2/5] hamradio: mkiss: remove redundant static initialization to 0
Date: Sun, 29 Mar 2026 22:34:05 +0800 [thread overview]
Message-ID: <20260329143408.747197-3-mashiro.chen@mailbox.org> (raw)
In-Reply-To: <20260329143408.747197-1-mashiro.chen@mailbox.org>
Static variables are automatically initialized to 0 by the
compiler.
Remove the explicit initialization to comply with the Linux
Kernel coding standards.
Signed-off-by: Mashiro Chen <mashiro.chen@mailbox.org>
---
drivers/net/hamradio/mkiss.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/hamradio/mkiss.c b/drivers/net/hamradio/mkiss.c
index eac45d936..3721572ce 100644
--- a/drivers/net/hamradio/mkiss.c
+++ b/drivers/net/hamradio/mkiss.c
@@ -686,7 +686,7 @@ static void mkiss_put(struct mkiss *ax)
complete(&ax->dead);
}
-static int crc_force = 0; /* Can be overridden with insmod */
+static int crc_force; /* Can be overridden with insmod */
static int mkiss_open(struct tty_struct *tty)
{
--
2.53.0
next prev parent reply other threads:[~2026-03-29 14:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-29 14:34 [PATCH 0/5] hamradio: mkiss: modernize and clean up mkiss driver Mashiro Chen
2026-03-29 14:34 ` [PATCH 1/5] hamradio: mkiss: move assignments out of if conditions Mashiro Chen
2026-03-29 14:34 ` Mashiro Chen [this message]
2026-03-29 14:34 ` [PATCH 3/5] hamradio: mkiss: fix spacing around assignment operator Mashiro Chen
2026-03-29 14:34 ` [PATCH 4/5] hamradio: mkiss: modernize logging with netdev and pr macros Mashiro Chen
2026-03-29 14:34 ` [PATCH 5/5] hamradio: mkiss: cleanup indentation and coding style Mashiro Chen
2026-03-29 17:35 ` [PATCH 0/5] hamradio: mkiss: modernize and clean up mkiss driver Jakub Kicinski
2026-03-29 19:19 ` Mashiro Chen
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=20260329143408.747197-3-mashiro.chen@mailbox.org \
--to=mashiro.chen@mailbox.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-hams@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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