From: Andrew Lunn <andrew@lunn.ch>
To: "Leizhen (ThunderTown)" <thunder.leizhen@huawei.com>
Cc: Jakub Kicinski <kuba@kernel.org>, netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH] net: forcedeth: Give bot handlers a helping hand understanding the code
Date: Wed, 12 May 2021 03:22:05 +0200 [thread overview]
Message-ID: <YJstvUmKGp5Nr5yS@lunn.ch> (raw)
In-Reply-To: <e267c38d-5ddd-244a-d083-9dbe4ed9973c@huawei.com>
On Tue, May 11, 2021 at 09:48:11PM +0800, Leizhen (ThunderTown) wrote:
>
>
> On 2021/5/11 20:43, Andrew Lunn wrote:
> > Bots handlers repeatedly fail to understand nv_update_linkspeed() and
> > submit patches unoptimizing it for the human reader. Add a comment to
> > try to prevent this in the future.
> >
> > Signed-off-by: Andrew Lunn <andrew@lunn.ch>
> > ---
> > drivers/net/ethernet/nvidia/forcedeth.c | 3 +++
> > 1 file changed, 3 insertions(+)
> >
> > diff --git a/drivers/net/ethernet/nvidia/forcedeth.c b/drivers/net/ethernet/nvidia/forcedeth.c
> > index 8724d6a9ed02..0822b28f3b6a 100644
> > --- a/drivers/net/ethernet/nvidia/forcedeth.c
> > +++ b/drivers/net/ethernet/nvidia/forcedeth.c
> > @@ -3475,6 +3475,9 @@ static int nv_update_linkspeed(struct net_device *dev)
> > newls = NVREG_LINKSPEED_FORCE|NVREG_LINKSPEED_10;
> > newdup = 0;
> > } else {
> > + /* Default to the same as 10/Half if we cannot
> > + * determine anything else.
> > + */
> I think it would be better to remove the if branch above and then add comments here.
> Otherwise, it becomes more and more redundant.
I kind of agree with you. However, we have seen at least four times,
that bots and their master are incapable of understanding this code
and try to unoptimize its readabilty/understandability. So we need to
add redundancy so hopefully the masters of these bots will understand
this code, see that it is correct, and leave it alone.
The other option is to work on the bot. Look at all the cases it got
it wrong, the code is in fact correct, but the bot could not see
why. Figure out the common pattern for why it got it wrong, and fix
the bot.
Or we can also add tools to aid the master. We know the bot gets it
wrong sometimes. The master also seems to get it wrong, and blindly
changes the code without understanding it. The maintainers then reject
it. That rejection is logged, it is available in lore. A tool which
can search lore for a similar patch which has been rejected before
seems like it would be useful for all bots. It would cut down on
wasted time of bot masters generating wrong patches and maintainers
rejecting them.
Andrew
prev parent reply other threads:[~2021-05-12 1:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-11 12:43 [PATCH] net: forcedeth: Give bot handlers a helping hand understanding the code Andrew Lunn
2021-05-11 13:48 ` Leizhen (ThunderTown)
2021-05-12 1:22 ` Andrew Lunn [this message]
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=YJstvUmKGp5Nr5yS@lunn.ch \
--to=andrew@lunn.ch \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=thunder.leizhen@huawei.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.