From: Jakub Kicinski <kuba@kernel.org>
To: Suraj Sonawane <surajsonawane0215@gmail.com>
Cc: davem@davemloft.net, dsahern@kernel.org, edumazet@google.com,
pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: ipv6: fix inconsistent indentation in ipv6_gro_receive
Date: Sun, 3 Nov 2024 15:22:13 -0800 [thread overview]
Message-ID: <20241103152213.2911b601@kernel.org> (raw)
In-Reply-To: <20241031065124.4834-1-surajsonawane0215@gmail.com>
On Thu, 31 Oct 2024 12:21:24 +0530 Suraj Sonawane wrote:
> Fix the indentation to ensure consistent code style and improve
> readability, and to fix this warning:
>
> net/ipv6/ip6_offload.c:280 ipv6_gro_receive() warn: inconsistent indenting
Warning from what tool?
Unless it's gcc or clang let's leave the code be, it's fine.
--
pw-bot: cr
next prev parent reply other threads:[~2024-11-03 23:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 6:51 [PATCH] net: ipv6: fix inconsistent indentation in ipv6_gro_receive Suraj Sonawane
2024-11-03 23:22 ` Jakub Kicinski [this message]
2024-11-05 5:10 ` Suraj Sonawane
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=20241103152213.2911b601@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=surajsonawane0215@gmail.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;
as well as URLs for NNTP newsgroup(s).