From: Neil Armstrong <narmstrong@baylibre.com>
To: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Florian Fainelli <f.fainelli@gmail.com>,
Andrew Lunn <andrew@lunn.ch>, Guenter Roeck <linux@roeck-us.net>
Subject: Re: [RFC PATCH net-next 0/6] net: dsa: mv88e6060: cleanup and fix setup
Date: Tue, 3 Nov 2015 17:27:26 +0100 [thread overview]
Message-ID: <5638E06E.8010405@baylibre.com> (raw)
In-Reply-To: <20151102154121.GB3036@ketchup.mtl.sfl>
On 11/02/2015 04:41 PM, Vivien Didelot wrote:
> Hi Neil,
>
> Nice cleanup. I'll just be a bit picky here, so you may not consider my
> comment for this patchset, but maybe for the future ones. Unless I'm
> mistaken, there is no reason to group all these patches together.
>
> The first 4 patches are independent fixes, and thus could have been sent
> separately to netdev -net.
>
> Then the last 2 ones could have been squashed together, because I don't
> see a real value to seperate them since you duplicate some defines, e.g.
> REG_PORT. And this patch would be a candidate for netdev -net-next.
>
> Thanks,
> -v
>
Hi Vivien,
I understand your point of view, and it really makes sense.
But the first patch has a dependency on the DSA cleanup patchset, so
if I follow your point, I should submit 3 patchsets with a single
patchset for the poll_link complete removal. But the two other
patchsets will have a strong dependency on the poll_link removal...
This question is on which version of mv88e6060 and dsa should I base
the cleanup patchset ? before of after the poll_link removal ?
For the fixes, they are not critical at all, net-next would be enough.
Any advice is welcome at this point....
Thanks !
Neil
prev parent reply other threads:[~2015-11-03 16:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-02 10:57 [RFC PATCH net-next 0/6] net: dsa: mv88e6060: cleanup and fix setup Neil Armstrong
2015-11-02 14:57 ` Andrew Lunn
2015-11-02 15:41 ` Vivien Didelot
2015-11-03 16:27 ` Neil Armstrong [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=5638E06E.8010405@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--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;
as well as URLs for NNTP newsgroup(s).