From: Jakub Kicinski <kuba@kernel•org>
To: Haiyue Wang <haiyuewa@163•com>
Cc: netdev@vger•kernel.org, Jeremy Kerr <jk@codeconstruct•com.au>,
Matt Johnston <matt@codeconstruct•com.au>,
Andrew Lunn <andrew+netdev@lunn•ch>,
"David S. Miller" <davem@davemloft•net>,
Eric Dumazet <edumazet@google•com>,
Paolo Abeni <pabeni@redhat•com>,
linux-kernel@vger•kernel.org (open list)
Subject: Re: [PATCH net-next v1] mctp i2c: align function parameter indentation
Date: Mon, 19 Jan 2026 08:48:23 -0800 [thread overview]
Message-ID: <20260119084823.5c2aa9b8@kernel.org> (raw)
In-Reply-To: <20260119070022.378216-1-haiyuewa@163.com>
On Mon, 19 Jan 2026 15:00:06 +0800 Haiyue Wang wrote:
> Align parameters of mctp_i2c_header_create() to improve readability
> and match kernel coding style. No functional change.
Quoting documentation:
Clean-up patches
~~~~~~~~~~~~~~~~
Netdev discourages patches which perform simple clean-ups, which are not in
the context of other work. For example:
* Addressing ``checkpatch.pl``, and other trivial coding style warnings
* Addressing :ref:`Local variable ordering<rcs>` issues
* Conversions to device-managed APIs (``devm_`` helpers)
This is because it is felt that the churn that such changes produce comes
at a greater cost than the value of such clean-ups.
Conversely, spelling and grammar fixes are not discouraged.
See: https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#clean-up-patches
--
pw-bot: cr
prev parent reply other threads:[~2026-01-19 16:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-19 7:00 [PATCH net-next v1] mctp i2c: align function parameter indentation Haiyue Wang
2026-01-19 16:48 ` Jakub Kicinski [this message]
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=20260119084823.5c2aa9b8@kernel.org \
--to=kuba@kernel$(echo .)org \
--cc=andrew+netdev@lunn$(echo .)ch \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=haiyuewa@163$(echo .)com \
--cc=jk@codeconstruct$(echo .)com.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=matt@codeconstruct$(echo .)com.au \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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