From: Andrew Lunn <andrew@lunn.ch>
To: Marek Vasut <marex@denx.de>
Cc: Tristram.Ha@microchip.com, f.fainelli@gmail.com,
vivien.didelot@savoirfairelinux.com, Woojung.Huh@microchip.com,
UNGLinuxDriver@microchip.com, davem@davemloft.net,
netdev@vger.kernel.org
Subject: Re: [PATCH] net: dsa: ksz: Fix port membership
Date: Sat, 8 Dec 2018 12:00:53 +0100 [thread overview]
Message-ID: <20181208110053.GA16502@lunn.ch> (raw)
In-Reply-To: <a2ee74b2-a97b-c09c-922c-d94d77889427@denx.de>
On Sat, Dec 08, 2018 at 05:23:25AM +0100, Marek Vasut wrote:
> On 12/08/2018 01:13 AM, Tristram.Ha@microchip.com wrote:
> >> Do you have a git tree with all the KSZ patches based on -next
> >> somewhere, so I don't have to look for them in random MLs ?
> >
> > I just sent it this Monday and the subject for that patch is
> > "[PATCH RFC 6/6] net: dsa: microchip: Add switch offload forwarding support."
>
> Is all that collected in some git tree somewhere, so I don't have to
> look for various patches in varying states of decay throughout the ML?
Hi Marek, Tristram
It is unfortunate that we have two patchsets being submitted at the
same time, with overlapping functionality. Some degree of cooperation
is needed to handle this.
Could i ask you both to publish a git tree of your patches. And then
figure out how to submit them. Maybe as smaller sets, with the easy,
non-overlapping bits first?
Andrew
next prev parent reply other threads:[~2018-12-08 11:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-07 17:44 [PATCH] net: dsa: ksz: Fix port membership Marek Vasut
2018-12-07 19:37 ` Tristram.Ha
2018-12-07 19:43 ` Florian Fainelli
2018-12-08 0:01 ` Tristram.Ha
2018-12-07 19:56 ` Marek Vasut
2018-12-08 0:13 ` Tristram.Ha
2018-12-08 4:23 ` Marek Vasut
2018-12-08 11:00 ` Andrew Lunn [this message]
2018-12-10 12:43 ` Marek Vasut
2018-12-13 3:51 ` Marek Vasut
2018-12-07 20:05 ` Andrew Lunn
2018-12-08 0:08 ` Tristram.Ha
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=20181208110053.GA16502@lunn.ch \
--to=andrew@lunn.ch \
--cc=Tristram.Ha@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=Woojung.Huh@microchip.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=marex@denx.de \
--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).