From: "René van Dorst" <opensource@vdorst.com>
To: Stefan Roese <sr@denx.de>
Cc: netdev@vger.kernel.org, linux-mediatek@lists.infradead.org,
Sean Wang <sean.wang@mediatek.com>,
John Crispin <john@phrozen.org>,
Daniel Golle <daniel@makrotopia.org>
Subject: Re: [PATCH] net: ethernet: mediatek: Add MT7628/88 SoC support
Date: Wed, 14 Aug 2019 13:08:56 +0000 [thread overview]
Message-ID: <20190814130856.Horde.wzHL8_VRawJ8NIIk--BD18e@www.vdorst.com> (raw)
In-Reply-To: <3ff9a0fc-f5ff-3798-4409-ed5b900e0b05@denx.de>
Hi Stefan,
Quoting Stefan Roese <sr@denx.de>:
> Hi Rene,
>
> On 14.08.19 11:26, René van Dorst wrote:
<snip>
>> Great, Thanks for addressing this issue.
>>
>> I hope we can collaborate to also support mt76x8 in my PHYLINK
>> patches [0][1].
>> I am close to posting V2 of the patches but I am currently waiting on some
>> fiber modules to test the changes better.
>
> I do have a "hackish" DSA driver for the integrated switch (ESW) in my
> tree. If time permits, I'll work on upstreaming this one as well. And
> yes, hopefully we can collaborate on your PHYLINK work too.
It is not only the switch driver but also the Mediatek ethernet driver that is
converted to PHYLINK. So we have a conflict in each others work.
I don't no what the right way is to go but I was thinking about 2 options
1. Lets say your work goes in first. I rebase my patches on your changes.
We collaborate to create an extra PHYLINK patch ontop of my work
for your SOC.
2. My patches goes in first and you adapt your patches to that.
What do you think?
I have latest changes here [0].
Also my modules did arrive so I can test my changes.
> Thanks,
> Stefan
Greats,
René
[0]
https://github.com/vDorst/linux-1/commits/net-next-phylink-upstream-mediatek
next prev parent reply other threads:[~2019-08-14 13:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-17 11:02 [PATCH] net: ethernet: mediatek: Add MT7628/88 SoC support Stefan Roese
2019-07-17 12:15 ` Daniel Golle
2019-07-19 4:06 ` Stefan Roese
2019-08-13 13:09 ` Stefan Roese
2019-07-17 12:53 ` René van Dorst
2019-08-14 8:26 ` Stefan Roese
2019-08-14 9:26 ` René van Dorst
2019-08-14 10:48 ` Stefan Roese
2019-08-14 13:08 ` René van Dorst [this message]
2019-08-15 9:08 ` Stefan Roese
2019-07-18 23:36 ` David Miller
2019-07-19 5:52 ` kbuild test robot
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=20190814130856.Horde.wzHL8_VRawJ8NIIk--BD18e@www.vdorst.com \
--to=opensource@vdorst.com \
--cc=daniel@makrotopia.org \
--cc=john@phrozen.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=sean.wang@mediatek.com \
--cc=sr@denx.de \
/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).