Re: [PATCH RFC 25/28] Documentation: DSA: Describe how probe of DSA and switches work.

> > It sounds like you want to 'optimise' for a DSA cluster consisting of > > a single switch, throwing away the D in DSA. Now the SF2 is a bit > > 'odd'. Since it is embedded in the SoC, you cannot have multiple of > > them in a cluster. So such an optimization could make sense for the > > SF2.

RE: [net-next 8/9] ixgbe: fix write to VLVFB in ixgbe_clear_vf_vlans()

>-Original Message- >From: Kirsher, Jeffrey T >Sent: Thursday, December 24, 2015 9:30 PM >To: da...@davemloft.net >Cc: Tantilov, Emil S; netdev@vger.kernel.org; nhor...@redhat.com; >sassm...@redhat.com; jogre...@redhat.com; Kirsher, Jeffrey T >Subject: [net-next 8/9] ixgbe: fix write to

Re: [PATCH net-next v5 2/8] netfilter: Factor out nf_ct_get_info().

On Wed, Dec 16, 2015 at 04:36:41PM -0800, Jarno Rajahalme wrote: > Define a new inline function to map conntrack status to enum > ip_conntrack_info. This removes the need to otherwise duplicate this > code in a later patch ("openvswitch: Find existing conntrack entry > after upcall."). > >

Re: [Intel-wired-lan] [PATCH v2] ixgbe: on recv increment rx.ring->stats.yields

Hi, please, let me know if I need to fix something else here. On 12/11/2015 05:05 PM, Pavel Tikhomirov wrote: It seem to be non intentionaly changed to tx in commit adc810900a70 ("ixgbe: Refactor busy poll socket code to address multiple issues") Lock is taken from ixgbe_low_latency_recv, and

Re: [PATCH RFC 00/28] DSA: Restructure probing

> > One of my aims is to abstract away the MDIO bus from DSA. How you talk > > to the switch is a switch device property. SF2 has a different way to > > talk to the switch, memory mapped IO, etc. > > I appreciate you trying to see my point of view and mentioning the > driver that I care about,

Re: [PATCH RFC 00/28] DSA: Restructure probing

> I am not really questioning whether the abstraction is working, this > clearly does, what I am wondering is if the use of the component > framework requires us to have master and slaves be implemented as strict > platform devices, or if we have a choice in how we mix things together, > like

[no subject]

-- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

[PATCH] prism54: fix checks for dma mapping errors

prism54 checks for dma mapping errors by comparison returned address with zero, while pci_dma_mapping_error() should be used. Found by Linux Driver Verification project (linuxtesting.org). Signed-off-by: Alexey Khoroshilov --- drivers/net/wireless/prism54/islpci_dev.c |

Re: [PATCH net-next 0/2] Local checksum offload for VXLAN

From: Tom Herbert Date: Thu, 17 Dec 2015 10:06:13 -0800 > On Thu, Dec 17, 2015 at 7:27 AM, Edward Cree wrote: >> When the inner packet checksum is offloaded, the outer UDP checksum is easy >> to calculate as it doesn't depend on the payload (because

Re: [PATCH RFC 26/28] dsa: Convert mv88e6xxx into a library allowing driver modules

Le 23/12/2015 04:56, Andrew Lunn a écrit : > Turn mv88e6xxx into a library module, by exporting its symbols. Have > each driver register their own driver functions with the DSA core in > there init function. > > This results in each driver being a loadable module. > > Signed-off-by: Andrew Lunn

Re: [PATCH RFC 00/28] DSA: Restructure probing

Le 25/12/2015 03:31, Andrew Lunn a écrit : >>> One of my aims is to abstract away the MDIO bus from DSA. How you talk >>> to the switch is a switch device property. SF2 has a different way to >>> talk to the switch, memory mapped IO, etc. >> >> I appreciate you trying to see my point of view and

Small improvements for the at803x PHY driver

Hello, while trying to debug a problem on a board with an AR8030 PHY (which turned out to be an incorrectly configured MDC clock) I made a few changes to the at803x driver. Due to lack of other hardware I could only test these changes with an AR8030 chip. Martin -- To unsubscribe from this

[PATCH 1/4] net: phy: at803x: Don't set gbit features for the AR8030 phy

The 8030 is only a "RMII Fast Ethernet PHY", thus it must not have the SUPPORTED_1000* bits set. Signed-off-by: Martin Blumenstingl --- drivers/net/phy/at803x.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/net/phy/at803x.c

[PATCH 4/4] net: phy: at803x: Add the interrupt register bit definitions

Also use them instead of a magic value when enabling the interrupts. Signed-off-by: Martin Blumenstingl --- drivers/net/phy/at803x.c | 32 +++- 1 file changed, 23 insertions(+), 9 deletions(-) diff --git a/drivers/net/phy/at803x.c

[PATCH 2/4] net: phy: at803x: Allow specifying the RGMII RX clock delay via phy mode

at803x currently automatically enables the RGMII TX clock delay when the phy interface mode is PHY_INTERFACE_MODE_RGMII_TXID. The same should be done when PHY_INTERFACE_MODE_RGMII_ID is specified. Use a similar logic to enable the RGMII RX clock delay as well. at803x_context_{save,restore} were

[PATCH 3/4] net: phy: at803x: Clean up duplicate register definitions

Signed-off-by: Martin Blumenstingl --- drivers/net/phy/at803x.c | 19 +++ 1 file changed, 11 insertions(+), 8 deletions(-) diff --git a/drivers/net/phy/at803x.c b/drivers/net/phy/at803x.c index 0b262a2..6e8aafd 100644 ---

Re: [PATCH net-next v3] ip_tunnel: Move stats update to iptunnel_xmit()

From: Pravin B Shelar Date: Thu, 24 Dec 2015 14:34:54 -0800 > By moving stats update into iptunnel_xmit(), we can simplify > iptunnel_xmit() usage. With this change there is no need to > call another function (iptunnel_xmit_stats()) to update stats > in tunnel xmit code path.

Re: [net-next 0/9][pull request] 10GbE Intel Wired LAN Driver Updates 2015-12-24

From: Jeff Kirsher Date: Thu, 24 Dec 2015 21:29:47 -0800 > This series contains updates to ixgbe and ixgbevf. Looks like patch #8 needs an update, so I'll wait for your respin of this series. Thanks. -- To unsubscribe from this list: send the line "unsubscribe