From: Jozsef Kadlecsik <kadlec@netfilter.org>
To: "Szőke Benjamin" <egyszeregy@freemail.hu>
Cc: fw@strlen.de, pablo@netfilter.org, lorenzo@kernel.org,
daniel@iogearbox.net, leitao@debian.org, amiculas@cisco.com,
davem@davemloft.net, dsahern@kernel.org, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 08/10] netfilter: Adjust code style of xt_*.h, ipt_*.h files.
Date: Wed, 8 Jan 2025 21:20:33 +0100 (CET) [thread overview]
Message-ID: <27838d8f-7664-fdb9-3f8a-5ca812acdf72@netfilter.org> (raw)
In-Reply-To: <4cf2e26b-2727-4b50-9ada-56a6be814dca@freemail.hu>
[-- Attachment #1: Type: text/plain, Size: 1305 bytes --]
On Tue, 7 Jan 2025, Szőke Benjamin wrote:
> 2025. 01. 07. 20:39 keltezéssel, Jozsef Kadlecsik írta:
> > On Tue, 7 Jan 2025, egyszeregy@freemail.hu wrote:
> >
> > > From: Benjamin Szőke <egyszeregy@freemail.hu>
> > >
> > > - Adjust tab indents
> > > - Fix format of #define macros
> >
> > I don't really understand why it'd be important to use parentheses
> > around plain constant values in macros. The kernel coding style does
> > not list it as a requirement, see 12) 4. in
> > Documentation/process/coding-style.rst.
>
> If it would be more than just a const value, parentheses is a must have
> thing for it (now for it, it is not critical to have it but better to
> get used to this). This is how my hand automatically do it, to avoid the
> syntax problem in this coding.
Are you going to "fix" this "issue" in the whole kernel tree?
If yes, then please propose changes to the coding style documentation as
well.
If no, then please keep the macros as is because the changes would just
introduce more different kind of notations in the source tree.
Best regards,
Jozsef
--
E-mail : kadlec@netfilter.org, kadlec@blackhole.kfki.hu, kadlecsik.jozsef@wigner.hu
Address: Wigner Research Centre for Physics
H-1525 Budapest 114, POB. 49, Hungary
next prev parent reply other threads:[~2025-01-08 20:20 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-07 2:41 [PATCH 00/10] netfilter: x_tables: Merge xt_*.h and ipt_*.h files which has same name egyszeregy
2025-01-07 2:41 ` [PATCH 01/10] netfilter: x_tables: Merge xt_DSCP.h to xt_dscp.h egyszeregy
2025-01-07 19:23 ` Jozsef Kadlecsik
2025-01-07 21:38 ` Szőke Benjamin
2025-01-08 20:11 ` Jozsef Kadlecsik
2025-01-08 21:08 ` Szőke Benjamin
2025-01-09 14:59 ` Jozsef Kadlecsik
2025-01-07 2:41 ` [PATCH 02/10] netfilter: x_tables: Merge xt_RATEEST.h to xt_rateest.h egyszeregy
2025-01-07 2:41 ` [PATCH 03/10] netfilter: x_tables: Merge xt_TCPMSS.h to xt_tcpmss.h egyszeregy
2025-01-07 2:41 ` [PATCH 04/10] netfilter: x_tables: Use consistent header guard egyszeregy
2025-01-07 2:41 ` [PATCH 05/10] netfilter: iptables: Merge ipt_ECN.h to ipt_ecn.h egyszeregy
2025-01-07 19:26 ` Jozsef Kadlecsik
2025-01-07 21:48 ` Szőke Benjamin
2025-01-08 20:15 ` Jozsef Kadlecsik
2025-01-07 2:41 ` [PATCH 06/10] netfilter: iptables: Merge ipt_TTL.h to ipt_ttl.h egyszeregy
2025-01-07 2:41 ` [PATCH 07/10] netfilter: iptables: Merge ip6t_HL.h to ip6t_hl.h egyszeregy
2025-01-07 2:41 ` [PATCH 08/10] netfilter: Adjust code style of xt_*.h, ipt_*.h files egyszeregy
2025-01-07 19:39 ` Jozsef Kadlecsik
2025-01-07 21:59 ` Szőke Benjamin
2025-01-08 20:20 ` Jozsef Kadlecsik [this message]
2025-01-08 21:18 ` Szőke Benjamin
2025-01-07 2:41 ` [PATCH 09/10] netfilter: Add message pragma for deprecated xt_*.h, ipt_*.h egyszeregy
2025-01-07 19:39 ` Jozsef Kadlecsik
2025-01-07 22:06 ` Szőke Benjamin
2025-01-07 22:38 ` Jan Engelhardt
2025-01-07 23:24 ` Szőke Benjamin
2025-01-08 20:51 ` Jozsef Kadlecsik
2025-01-08 21:38 ` Szőke Benjamin
2025-01-09 10:22 ` Przemek Kitszel
2025-01-07 2:41 ` [PATCH 10/10] netfilter: Use merged xt_*.h, ipt_*.h headers egyszeregy
2025-01-07 19:14 ` [PATCH 00/10] netfilter: x_tables: Merge xt_*.h and ipt_*.h files which has same name Jozsef Kadlecsik
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=27838d8f-7664-fdb9-3f8a-5ca812acdf72@netfilter.org \
--to=kadlec@netfilter.org \
--cc=amiculas@cisco.com \
--cc=coreteam@netfilter.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=egyszeregy@freemail.hu \
--cc=fw@strlen.de \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.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
all inboxes | Powered by JetHome®