From: Andrew Lunn <andrew@lunn.ch>
To: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel@savoirfairelinux.com,
"David S. Miller" <davem@davemloft.net>,
Florian Fainelli <f.fainelli@gmail.com>
Subject: Re: [PATCH net-next 04/14] net: dsa: mv88e6xxx: rework ATU Load/Purge
Date: Sun, 12 Mar 2017 00:40:21 +0100 [thread overview]
Message-ID: <20170311234021.GE15842@lunn.ch> (raw)
In-Reply-To: <87zigrzg6s.fsf@weeman.i-did-not-set--mail-host-address--so-tickle-me>
> > I really wished you had moved the code, unmodified, into
> > global1_atu.c. Then made lots of easy to review small changes. I
> > cannot just look at this patch and know it is correct. What i need to
> > compare against is not in this patch. So it is a lot harder to review.
>
> I've addressed all of your comments in this patchset except this one.
Hi Vivien
This time, i'm not going to push the issue further. But next time i
will.
The point is, we have working code. You don't just throw that
away. You make lots of small changes to that working code to morph it
into the code you want. These small changes are all very quick and
easy to review, because they are all small and obvious. At each stage
we have working code. If somehow it does break, it is easy to bisect
it down to one small change. The actual likelyhood of breaking it is
small, because the changes are all small and obviously correct.
It does result in more patches, more to review, but it is much easier
to review, because it should be obviously correct. The overall lines
of code at the end is the same. So overall there is no harm is having
lots of small patches.
> A patch file cannot guarantee that a chunk of code moved around has not
> been altered in the process. This will just generate more diff for no
> value, that needs to be updated afterwards anyway.
I don't need a guarantee. I would trust you have moved it, without
editing it. Generating more diff is not a problem. The number of diffs
is not important at all. What is important is lots of small, easy to
review, obviously correct patches.
> Plus you already complained in the first iteration I sent about
> modifying lines that I previously added. I took care of logically
> splitting the new ATU Load/Purge, GetNext, Flush and Remove operations
> into incremental unmodified chunks in this series.
Unfortunately, you are splitting in the wrong dimension. None of this
is obviously correct. But it easily code of been.
Andrew
next prev parent reply other threads:[~2017-03-11 23:40 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-09 23:33 [PATCH net-next 00/14] net: dsa: mv88e6xxx: rework ATU support Vivien Didelot
2017-03-09 23:33 ` [PATCH net-next 01/14] net: dsa: mv88e6xxx: add port mask helper Vivien Didelot
2017-03-09 23:33 ` [PATCH net-next 02/14] net: dsa: mv88e6xxx: move ATU ageing time setter Vivien Didelot
2017-03-10 0:45 ` Andrew Lunn
2017-03-09 23:33 ` [PATCH net-next 03/14] net: dsa: mv88e6xxx: setup ATU Learn2All Vivien Didelot
2017-03-10 2:00 ` Andrew Lunn
2017-03-10 2:03 ` Andrew Lunn
2017-03-09 23:33 ` [PATCH net-next 04/14] net: dsa: mv88e6xxx: rework ATU Load/Purge Vivien Didelot
2017-03-10 2:27 ` Andrew Lunn
2017-03-11 20:55 ` Vivien Didelot
2017-03-11 23:40 ` Andrew Lunn [this message]
2017-03-13 14:59 ` Vivien Didelot
2017-03-09 23:33 ` [PATCH net-next 05/14] net: dsa: mv88e6xxx: rework ATU GetNext Vivien Didelot
2017-03-09 23:33 ` [PATCH net-next 06/14] net: dsa: mv88e6xxx: rework ATU Flush Vivien Didelot
2017-03-09 23:33 ` [PATCH net-next 07/14] net: dsa: mv88e6xxx: rework ATU Remove Vivien Didelot
2017-03-10 2:33 ` Andrew Lunn
2017-03-09 23:33 ` [PATCH net-next 08/14] net: dsa: mv88e6xxx: rename new FID helper Vivien Didelot
2017-03-10 0:16 ` Andrew Lunn
2017-03-09 23:33 ` [PATCH net-next 09/14] net: dsa: mv88e6xxx: rename the port vector member Vivien Didelot
2017-03-10 0:17 ` Andrew Lunn
2017-03-09 23:33 ` [PATCH net-next 10/14] net: dsa: mv88e6xxx: rework port mode setup Vivien Didelot
2017-03-10 0:29 ` Andrew Lunn
2017-03-09 23:33 ` [PATCH net-next 11/14] net: dsa: mv88e6xxx: fix port egress flooding mode Vivien Didelot
2017-03-09 23:33 ` [PATCH net-next 12/14] net: dsa: mv88e6xxx: add port ATU learn limit op Vivien Didelot
2017-03-10 0:37 ` Andrew Lunn
2017-03-09 23:33 ` [PATCH net-next 13/14] net: dsa: mv88e6xxx: add port priority override op Vivien Didelot
2017-03-10 0:39 ` Andrew Lunn
2017-03-09 23:33 ` [PATCH net-next 14/14] etherdevice: remove unused eth_addr_greater Vivien Didelot
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=20170311234021.GE15842@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kernel@savoirfairelinux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@savoirfairelinux.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