From: Qasim Ijaz <qasdev00@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, linux-usb@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: ch9200: use BIT macro for bitmask constants
Date: Fri, 6 Jun 2025 18:19:25 +0100 [thread overview]
Message-ID: <aEMjFjQo1QZoKEXw@gmail.com> (raw)
In-Reply-To: <486738a4-c3ea-4af2-ba78-53bf8522ccb1@lunn.ch>
On Fri, Jun 06, 2025 at 06:46:25PM +0200, Andrew Lunn wrote:
> On Fri, Jun 06, 2025 at 05:07:23PM +0100, Qasim Ijaz wrote:
> > Use the BIT() macro for bitmask constants.
>
> What you fail to answer is the question 'Why?'.
I made this change mainly as a small clean-up, it makes the code a tad
bit easier to read.
>
> This driver is old and stable. It has in fact had no feature
> development work done on it since 2015. All the patches since then
> have been tree wide sort of changes.
>
> Most would consider your change just pointless churn. It does not fix
> anything which is broken. So why make this change?
Yea that makes sense.
>
> https://www.kernel.org/doc/html/latest/process/maintainer-netdev.html#clean-up-patches
Ah i see thank you, I will keep this in mind next time.
>
> Do you have the hardware? If you do, maybe consider porting it to
> phylib?
>
I don't, I did try to buy it but after searching for it but I couldn't
find it anywhere. I do however have the hardware for the this:
https://web.git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/usb/dm9601.c
Would the phylib porting apply to this too? If so I would love to work
on it.
Thanks
Qasim
> Andrew
next prev parent reply other threads:[~2025-06-06 17:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-06 16:07 [PATCH] net: ch9200: use BIT macro for bitmask constants Qasim Ijaz
2025-06-06 16:46 ` Andrew Lunn
2025-06-06 17:19 ` Qasim Ijaz [this message]
2025-06-06 19:00 ` Andrew Lunn
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=aEMjFjQo1QZoKEXw@gmail.com \
--to=qasdev00@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).