[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <8bbcefc0-b004-ce29-02a0-7d6743f29bee@blackhole.kfki.hu>
Date: Sat, 4 Jan 2025 15:38:37 +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,
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 v2] netfilter: uapi: Merge xt_*.h/c and ipt_*.h which
has same name.
On Thu, 2 Jan 2025, Szőke Benjamin wrote:
> > This needs a much stronger argument, since as i already pointed out,
> > how many case-insenstive file systems are still in use? Please give
> > real world examples of why this matters.
>
> All of MacOS and Windows platform are case-insensitive. So it means, who
> like to edit Linux kernel code on them, then build it in a remote SSH
> solution, there are lot of them.
As far as I known on Windows 10 and above one can enable case-sensitivity
for given folders. If one uses WSL, then it's default on and true for all
subfolders as well. On MacOS one can create case-sensitive volumes.
So if someone wants to develop Linux kernel on these systems, with a
little effort, one can create the proper environment for it including the
case-sensitive directory structure/filesystem.
In my opinion merging the match/target files and thus shrinking the code,
saving memory are more interesting in your efforts than your original goal
- without sprinkling the code with warnings in pragmas.
Best regards,
Jozsef
Powered by blists - more mailing lists