From: David Miller <davem@davemloft.net>
To: nbd@openwrt.org
Cc: andrew@lunn.ch, blogic@openwrt.org, netdev@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
matthias.bgg@gmail.com, steven.liu@mediatek.com,
Carlos.Huang@mediatek.com, Fred.Chang@mediatek.com
Subject: Re: [PATCH V2 03/12] net-next: mediatek: add embedded switch driver (ESW)
Date: Fri, 26 Feb 2016 12:43:13 -0500 (EST) [thread overview]
Message-ID: <20160226.124313.718457444189293093.davem@davemloft.net> (raw)
In-Reply-To: <56D07C82.2040204@openwrt.org>
From: Felix Fietkau <nbd@openwrt.org>
Date: Fri, 26 Feb 2016 17:25:38 +0100
> In my opinion, leaving this part out does not make much sense and
> neither does deferring the entire patch series until we have a
> switchdev/DSA capable driver. This is just a starting point, which will
> be turned into a proper driver with the right APIs later.
I disagree, and we want people to concentrate on writing proper
switchdev/DSA drivers.
People like Andrew have offered to help in any way possible to make
this as easy as possible, so please take this seriously.
I would have accepted your arguments a year ago when we didn't have
the right infrastructure, but now we do and there is no real excuse
to submit partial or bastardized drivers for these kinds of hardware
anymore
Thanks in advance for your understanding, and I'm plan to stand
very firm on this.
next prev parent reply other threads:[~2016-02-26 17:43 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 14:21 [PATCH V2 00/12] net-next: mediatek: add ethernet driver John Crispin
2016-02-26 14:21 ` [PATCH V2 01/12] net-next: mediatek: Document ralink/mediatek SoC ethernet binding John Crispin
2016-03-02 18:46 ` Rob Herring
2016-03-02 18:49 ` John Crispin
2016-02-26 14:21 ` [PATCH V2 02/12] net-next: mediatek: add the drivers core files John Crispin
2016-02-26 14:21 ` [PATCH V2 03/12] net-next: mediatek: add embedded switch driver (ESW) John Crispin
2016-02-26 15:18 ` Andrew Lunn
2016-02-26 15:24 ` John Crispin
2016-02-26 17:05 ` Andrew Lunn
2016-02-26 17:44 ` David Miller
2016-02-26 17:36 ` David Miller
2016-02-26 18:34 ` Florian Fainelli
2016-02-26 16:25 ` Felix Fietkau
2016-02-26 17:29 ` Andrew Lunn
2016-02-26 17:43 ` David Miller [this message]
2016-02-26 17:35 ` David Miller
2016-02-26 14:21 ` [PATCH V2 04/12] net-next: mediatek: add gigabit switch driver (GSW) John Crispin
2016-02-26 14:21 ` [PATCH V2 05/12] net-next: mediatek: add support for rt2880 John Crispin
2016-02-26 14:21 ` [PATCH V2 06/12] net-next: mediatek: add support for rt3050 John Crispin
2016-02-26 14:21 ` [PATCH V2 07/12] net-next: mediatek: add support for rt3883 John Crispin
2016-02-26 14:21 ` [PATCH V2 08/12] net-next: mediatek: add support for mt7620 John Crispin
2016-02-26 14:21 ` [PATCH V2 09/12] net-next: mediatek: add support for mt7621 John Crispin
2016-02-26 14:21 ` [PATCH V2 10/12] net-next: mediatek: add support for mt7623 John Crispin
2016-02-26 14:21 ` [PATCH V2 11/12] net-next: mediatek: add Kconfig and Makefile John Crispin
2016-02-27 3:29 ` kbuild test robot
2016-02-26 14:21 ` [PATCH V2 12/12] net-next: mediatek: add an entry to MAINTAINERS John Crispin
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=20160226.124313.718457444189293093.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Carlos.Huang@mediatek.com \
--cc=Fred.Chang@mediatek.com \
--cc=andrew@lunn.ch \
--cc=blogic@openwrt.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=nbd@openwrt.org \
--cc=netdev@vger.kernel.org \
--cc=steven.liu@mediatek.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).