[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ee78ed44-7eed-0a80-6525-61b5925df431@blackhole.kfki.hu>
Date: Mon, 6 Jan 2025 08:48:34 +0100 (CET)
From: Jozsef Kadlecsik <kadlec@...ckhole.kfki.hu>
To: Szőke Benjamin <egyszeregy@...email.hu>
cc: Andrew Lunn <andrew@...n.ch>, Florian Westphal <fw@...len.de>,
Pablo Neira Ayuso <pablo@...filter.org>, lorenzo@...nel.org,
daniel@...earbox.net, leitao@...ian.org, amiculas@...co.com,
kadlec@...filter.org, David Miller <davem@...emloft.net>,
dsahern@...nel.org, edumazet@...gle.com, kuba@...nel.org,
pabeni@...hat.com, horms@...nel.org, netfilter-devel@...r.kernel.org,
coreteam@...filter.org, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org
Subject: Re: [PATCH v5 1/3] netfilter: x_tables: Merge xt_*.h and ipt_*.h
files which has same name.
On Mon, 6 Jan 2025, Szőke Benjamin wrote:
> 2025. 01. 05. 22:27 keltezéssel, Andrew Lunn írta:
>> On Sun, Jan 05, 2025 at 09:34:52PM +0100, egyszeregy@...email.hu wrote:
>>> From: Benjamin Szőke <egyszeregy@...email.hu>
>>>
>>> Merge xt_*.h, ipt_*.h and ip6t_*.h header files, which has
>>> same upper and lower case name format.
>>>
>>> Add #pragma message about recommended to use
>>> header files with lower case format in the future.
>>
>> It looks like only patch 1/3 make it to the list.
>>
>> Also, with a patchset, please include a patch 0/X which gives the big
>> picture of what the patchset does. The text will be used for the merge
>> commit, so keep it formal. 'git format-patch --cover-letter' will
>> create the empty 0/X patch you can edit, or if you are using b4 prep,
>> you can use 'b4 prep --edit-cover' and then 'b4 send' will
>> automatically generate and send it.
>>
>> https://docs.kernel.org/process/maintainer-netdev.html
>> https://docs.kernel.org/process/submitting-patches.html
>>
>> Andrew
>
> https://lore.kernel.org/lkml/20250105233157.6814-1-egyszeregy@freemail.hu/T/
>
> It is terribly chaotic how slowly start to appear the full patch list in the
> mailing list website. It's really time to replace 1990s dev technology with
> something like GitLab or GitHub developing style can provide in 2024.
No, it was your fault in the v5 series of your patches: you managed to
send all the patches in a single email instead of separated ones.
Best regards,
Jozsef
Powered by blists - more mailing lists