From: Murali Krishna <muralikrishna2444b@gmail.com>
To: mani@kernel.org
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org,
linux-arm-msm@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
Murali Krishna <muralikrishna2444b@gmail.com>
Subject: [PATCH 0/1] net: qrtr: fix coding style issues flagged by checkpatch
Date: Sun, 13 Sep 2026 23:33:41 +0530 [thread overview]
Message-ID: <20260913180342.8948-1-muralikrishna2444b@gmail.com> (raw)
Hello,
This is my first patch to the kernel and I am still learning the
process, so please forgive any mistakes in formatting or etiquette.
This patch addresses a few minor coding style issues in net/qrtr/
that I found by running checkpatch --strict:
- Fix missing space in a pointer cast (ERROR)
- Move trailing "*/" to its own line in two block comments (WARNING)
- Add parameter names to a function pointer declaration (WARNING)
- Remove an unnecessary return at the end of a void function (WARNING)
After applying, both af_qrtr.c and ns.c pass checkpatch --strict
with zero errors, warnings, and checks.
I would be very grateful for any feedback or suggestions, even if
the patch is accepted as-is. I am happy to send a v2 if anything
needs to be changed.
Thank you for your time.
Kind regards,
Murali Krishna
Murali Krishna (1):
net: qrtr: fix coding style issues flagged by checkpatch
net/qrtr/af_qrtr.c | 12 +++++++-----
net/qrtr/ns.c | 2 --
2 files changed, 7 insertions(+), 7 deletions(-)
--
2.43.0
next reply other threads:[~2026-09-13 18:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-13 18:03 Murali Krishna [this message]
2026-09-13 18:03 ` [PATCH 1/1] net: qrtr: fix coding style issues flagged by checkpatch Murali Krishna
-- strict thread matches above, loose matches on Subject: below --
2026-09-13 18:03 [PATCH 0/1] " Murali Krishna
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=20260913180342.8948-1-muralikrishna2444b@gmail.com \
--to=muralikrishna2444b@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mani@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