From: Vincent Mailhol <mailhol@kernel.org>
To: netdev@vger.kernel.org,
Stephen Hemminger <stephen@networkplumber.org>,
David Ahern <dsahern@gmail.com>
Cc: Marc Kleine-Budde <mkl@pengutronix.de>,
Oliver Hartkopp <socketcan@hartkopp.net>,
linux-kernel@vger.kernel.org, linux-can@vger.kernel.org,
Vincent Mailhol <mailhol@kernel.org>
Subject: [PATCH iproute2-next 0/3] iplink_can: fix checkpatch.pl warnings
Date: Sun, 21 Sep 2025 16:32:29 +0900 [thread overview]
Message-ID: <20250921-iplink_can-checkpatch-fixes-v1-0-1ddab98560cd@kernel.org> (raw)
This is a clean up series which goes through all the checkpatch
warnings on ip/iplink_can.c and fixes them one by one. By the end on
this series, there is only one warning left:
WARNING: Prefer __printf(2, 0) over __attribute__((format(printf, 2, 0)))
#320: FILE: ip/iplink_can.c:320:
+static void __attribute__((format(printf, 2, 0)))
Because iproute2 does not declare the __printf() macro, that last one
can not be fixed.
Signed-off-by: Vincent Mailhol <mailhol@kernel.org>
---
Vincent Mailhol (3):
iplink_can: fix coding style for pointer format
iplink_can: fix SPDX-License-Identifier tag format
iplink_can: factorise the calls to usage()
ip/iplink_can.c | 12 +++++-------
1 file changed, 5 insertions(+), 7 deletions(-)
---
base-commit: afceddf61037440628a5612f15a6eaefd28d9fd3
change-id: 20250921-iplink_can-checkpatch-fixes-1ca804bd4fa4
Best regards,
--
Vincent Mailhol <mailhol@kernel.org>
next reply other threads:[~2025-09-21 7:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-21 7:32 Vincent Mailhol [this message]
2025-09-21 7:32 ` [PATCH iproute2-next 1/3] iplink_can: fix coding style for pointer format Vincent Mailhol
2025-09-22 22:10 ` Stephen Hemminger
2025-09-23 2:07 ` Vincent Mailhol
2025-09-21 7:32 ` [PATCH iproute2-next 2/3] iplink_can: fix SPDX-License-Identifier tag format Vincent Mailhol
2025-09-22 22:08 ` Stephen Hemminger
2025-09-21 7:32 ` [PATCH iproute2-next 3/3] iplink_can: factorise the calls to usage() Vincent Mailhol
2025-09-22 22:09 ` Stephen Hemminger
2025-09-22 8:42 ` [PATCH iproute2-next 0/3] iplink_can: fix checkpatch.pl warnings Marc Kleine-Budde
2025-09-25 16:40 ` patchwork-bot+netdevbpf
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=20250921-iplink_can-checkpatch-fixes-v1-0-1ddab98560cd@kernel.org \
--to=mailhol@kernel.org \
--cc=dsahern@gmail.com \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=socketcan@hartkopp.net \
--cc=stephen@networkplumber.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;
as well as URLs for NNTP newsgroup(s).