From: Simon Horman <horms@kernel.org>
To: Moon Yeounsu <yyyynoom@gmail.com>
Cc: cooldavid@cooldavid.org, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: ethernet: use ip_hdrlen() instead of bit shift
Date: Sun, 4 Aug 2024 11:18:58 +0100 [thread overview]
Message-ID: <20240804101858.GI2504122@kernel.org> (raw)
In-Reply-To: <CAAjsZQwKbp-3QgBj9KEUoqLvaE5pLX8wsLq01TDC8HdVp=8pLg@mail.gmail.com>
On Sat, Aug 03, 2024 at 10:47:35AM +0900, Moon Yeounsu wrote:
> On Fri, Aug 2, 2024 at 11:15 PM Simon Horman <horms@kernel.org> wrote:
> >
> > On Fri, Aug 02, 2024 at 02:44:21PM +0900, Moon Yeounsu wrote:
> > > `ip_hdr(skb)->ihl << 2` are the same as `ip_hdrlen(skb)`
> > > Therefore, we should use a well-defined function not a bit shift
> > > to find the header length.
> > >
> > > It also compress two lines at a single line.
> > >
> > > Signed-off-by: Moon Yeounsu <yyyynoom@gmail.com>
> >
> > Firstly, I think this clean-up is both correct and safe. Safe because
> > ip_hdrlen() only relies on ip_hdr(), which is already used in the same code
> > path. And correct because ip_hdrlen multiplies ihl by 4, which is clearly
> > equivalent to a left shift of 2 bits.
> Firstly, Thank you for reviewing my patch!
> >
> > However, I do wonder about the value of clean-ups for what appears to be a
> > very old driver, which hasn't received a new feature for quite sometime
> Oh, I don't know that...
> >
> > And further, I wonder if we should update this driver from "Maintained" to
> > "Odd Fixes" as the maintainer, "Guo-Fu Tseng" <cooldavid@cooldavid.org>,
> > doesn't seem to have been seen by lore since early 2020.
> >
> > https://lore.kernel.org/netdev/20200219034801.M31679@cooldavid.org/
> Then, how about deleting the file from the kernel if the driver isn't
> maintained?
That is a bit more severe than marking it as being unmaintained
in MAINTAINERS. But I do agree that it should be considered.
> Many people think like that (At least I think so)
> There are files, and if there are issues, then have to fix them.
> Who can think unmanaged files remain in the kernel?
And yet, they do exist. ☯
next prev parent reply other threads:[~2024-08-04 10:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-02 5:44 [PATCH] net: ethernet: use ip_hdrlen() instead of bit shift Moon Yeounsu
2024-08-02 13:35 ` Christophe JAILLET
2024-08-03 1:21 ` Moon Yeounsu
2024-08-02 14:15 ` Simon Horman
2024-08-02 14:40 ` Simon Horman
2024-08-03 1:47 ` Moon Yeounsu
2024-08-04 10:18 ` Simon Horman [this message]
2024-08-05 0:32 ` Guo-Fu Tseng
2024-08-03 2:29 ` [PATCH v2] net: ethernet: remove unnecessary parentheses Moon Yeounsu
2024-08-03 10:22 ` Christophe JAILLET
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=20240804101858.GI2504122@kernel.org \
--to=horms@kernel.org \
--cc=cooldavid@cooldavid.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=yyyynoom@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.