[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1454174735.7329.20.camel@perches.com>
Date: Sat, 30 Jan 2016 09:25:35 -0800
From: Joe Perches <joe@...ches.com>
To: Lucas Tanure <tanure@...ux.com>, Patrick McHardy <kaber@...sh.net>
Cc: Pablo Neira Ayuso <pablo@...filter.org>,
Jozsef Kadlecsik <kadlec@...ckhole.kfki.hu>,
"David S . Miller" <davem@...emloft.net>,
Alexey Kuznetsov <kuznet@....inr.ac.ru>,
coreteam@...filter.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/4] netfilter: ipv4: use preferred kernel types
On Sat, 2016-01-30 at 12:05 -0200, Lucas Tanure wrote:
> On Sat, Jan 30, 2016 at 11:45 AM, Patrick McHardy <kaber@...sh.net> wrote:
> > On 30.01, Lucas Tanure wrote:
> > > As suggested by checkpatch.pl:
> > > CHECK: Prefer kernel type 'uX' over 'uintX_t'
> >
> > You might have noticed we have literally hundreds of them spread over 100
> > files in the netfilter code. We'll gradually change them when the code is
> > touched anyways.
> >
> > > net/ipv4/netfilter/ip_tables.c | 5 ++---
> > > 1 file changed, 2 insertions(+), 3 deletions(-)
>
> Yes, I checked that. But would be better to change that now?
> Because:
> - could take years to anyone to touch the code, as the code already
> works very well
> - be more standardized could facilitate reading the code
> - It's a good way to encourage new people to contribute to the code
The last one bullet point is what staging is for.
It might be better to do them all at once:
$ git grep --name-only "\bu_int" net/netfilter/ | \
xargs perl -p -i -e 's/\bu_int(\d+)_t\b/u\1/g'
Powered by blists - more mailing lists