Re: [PATCH v3 0/5] meson: Meson8b and GXBB DWMAC glue driver
From: David Miller <hidden>
Date: 2016-08-31 04:57:32
Also in:
linux-amlogic, linux-arm-kernel, netdev
From: Martin Blumenstingl <martin.blumenstingl-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org> Date: Tue, 30 Aug 2016 20:49:28 +0200
On Mon, Aug 29, 2016 at 5:40 AM, David Miller [off-list ref] wrote:quoted
From: Martin Blumenstingl <martin.blumenstingl-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org> Date: Sun, 28 Aug 2016 18:16:32 +0200quoted
This adds a DWMAC glue driver for the PRG_ETHERNET registers found in Meson8b and GXBB SoCs. Based on the "old" meson6b-dwmac glue driver the register layout is completely different. Thus I introduced a separate driver. Changes since v2: - fixed unloading the glue driver when built as module. This pulls in a patch from Joachim Eastwood (thanks) to get our private data structure (bsp_priv).This doesn't apply cleanly at all to the net-next tree, so I have no idea where you expect these changes to be applied.OK, maybe Kevin can me help out here as I think the patches should go to various trees. I think patches 1, 3 and 4 should go through the net-next tree (as these touch drivers/net/ethernet/stmicro/stmmac/ and the corresponding documentation). Patch 2 should probably go through clk-meson-gxbb / clk-next (just like the other clk changes we had). The last patch (patch 5) should probably go through the ARM SoC tree (just like the other dts changes we had). @David, Kevin: would this be fine for you?
I would prefer if all of the patches went through one tree, that way all the dependencies are satisfied in one place. -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html