Re: [PATCH RFC 1/5] net: phy: sun8i-h3-ephy: Add bindings for Allwinner H3 Ethernet PHY

Hi, On Tue, Apr 12, 2016 at 9:38 AM, Chen-Yu Tsai wrote: > On Tue, Apr 12, 2016 at 3:23 AM, Florian Fainelli > wrote: >> On 04/04/16 09:22, Chen-Yu Tsai wrote: >>> The Allwinner H3 SoC incorporates an Ethernet PHY. This is enabled and >>> configured through

[PATCH net-next] tcp: refactor struct tcp_skb_cb

Refactor tcp_skb_cb to create two overlaping areas to store state for incoming or outgoing skbs based on comments by Neal Cardwell to tcp_nv patch: AFAICT this patch would not require an increase in the size of sk_buff cb[] if it were to take advantage of the fact that the tcp_skb_cb

[PATCH net-next] tcp: replace cnt & rtt with struct in pkts_acked()

Replace 2 arguments (cnt and rtt) in the congestion control modules' pkts_acked() function with a struct. This will allow adding more information without having to modify existing congestion control modules (tcp_nv in particular needs bytes in flight when packet was sent). As proposed by Neal

Re: [PATCH v3 net-next 00/11] ipv6: Enable GUEoIPv6 and more fixes for v6 tunneling

On Fri, May 6, 2016 at 7:11 PM, Tom Herbert wrote: > On Fri, May 6, 2016 at 7:03 PM, Alexander Duyck > wrote: >> On Fri, May 6, 2016 at 6:57 PM, Tom Herbert wrote: >>> On Fri, May 6, 2016 at 6:09 PM, Alexander Duyck >>>

Re: [PATCH v3 net-next 01/11] gso: Remove arbitrary checks for unsupported GSO

On Fri, May 6, 2016 at 3:11 PM, Tom Herbert wrote: > diff --git a/net/mpls/mpls_gso.c b/net/mpls/mpls_gso.c > index bbcf604..6de1e13 100644 > --- a/net/mpls/mpls_gso.c > +++ b/net/mpls/mpls_gso.c > @@ -26,15 +26,6 @@ static struct sk_buff *mpls_gso_segment(struct sk_buff >

Re: [PATCH v3 net-next 00/11] ipv6: Enable GUEoIPv6 and more fixes for v6 tunneling

On Fri, May 6, 2016 at 7:03 PM, Alexander Duyck wrote: > On Fri, May 6, 2016 at 6:57 PM, Tom Herbert wrote: >> On Fri, May 6, 2016 at 6:09 PM, Alexander Duyck >> wrote: >>> On Fri, May 6, 2016 at 3:11 PM, Tom Herbert

Re: [PATCH v3 net-next 00/11] ipv6: Enable GUEoIPv6 and more fixes for v6 tunneling

On Fri, May 6, 2016 at 6:57 PM, Tom Herbert wrote: > On Fri, May 6, 2016 at 6:09 PM, Alexander Duyck > wrote: >> On Fri, May 6, 2016 at 3:11 PM, Tom Herbert wrote: >>> This patch set: >>> - Fixes GRE6 to process translate

Re: [PATCH v3 net-next 00/11] ipv6: Enable GUEoIPv6 and more fixes for v6 tunneling

On Fri, May 6, 2016 at 6:09 PM, Alexander Duyck wrote: > On Fri, May 6, 2016 at 3:11 PM, Tom Herbert wrote: >> This patch set: >> - Fixes GRE6 to process translate flags correctly from configuration >> - Adds support for GSO and GRO for ip6ip6

[PATCH net-next 2/2] net: original ingress device index in PKTINFO

Applications such as OSPF and BFD need the original ingress device not the VRF device; the latter can be derived from the former. To that end add the skb_iif to inet_skb_parm and set it in ipv4 code after clearing the skb control buffer similar to IPv6. From there the pktinfo can just pull it from

[PATCH net-next v2 1/2] net: l3mdev: Add hook in ip and ipv6

Currently the VRF driver uses the rx_handler to switch the skb device to the VRF device. Switching the dev prior to the ip / ipv6 layer means the VRF driver has to duplicate IP/IPv6 processing which adds overhead and makes features such as retaining the ingress device index more complicated than

[PATCH net-next v2 0/2] net: vrf: Fixup PKTINFO to return enslaved device index

Applications such as OSPF and BFD need the original ingress device not the VRF device; the latter can be derived from the former. To that end move the packet intercept from an rx handler that is invoked by __netif_receive_skb_core to the ipv4 and ipv6 receive processing. IPv6 already saves the

[PATCH v2 net-next] ifb: support more features

From: Eric Dumazet When using ifb+netem on ingress on SIT/IPIP/GRE traffic, GRO packets are not properly processed. Segmentation should not be forced, since ifb is already adding quite a performance hit. Signed-off-by: Eric Dumazet ---

Re: [PATCH v3 net-next 00/11] ipv6: Enable GUEoIPv6 and more fixes for v6 tunneling

On Fri, May 6, 2016 at 3:11 PM, Tom Herbert wrote: > This patch set: > - Fixes GRE6 to process translate flags correctly from configuration > - Adds support for GSO and GRO for ip6ip6 and ip4ip6 > - Add support for FOU and GUE in IPv6 > - Support GRE, ip6ip6 and

Re: [PATCH net-next 0/2] net: vrf: Fixup PKTINFO to return enslaved device index

On 5/5/16 1:37 PM, David Ahern wrote: Applications such as OSPF and BFD need the original ingress device not the VRF device; the latter can be derived from the former. To that end move the packet intercept from an rx handler that is invoked by __netif_receive_skb_core to the ipv4 and ipv6

Re: [PATCH net-next] ifb: support more features

On Fri, 2016-05-06 at 16:41 -0700, Eric Dumazet wrote: > From: Eric Dumazet > > When using ifb+netem on ingress on SIT/IPIP/GRE traffic, > GRO packets are not properly processed. > > Segmentation should not be forced, as ifb is already adding > quite a performance hit.

Re: [PATCH net-next] net: make sch_handle_ingress() drop monitor ready

On Fri, May 06, 2016 at 03:55:50PM -0700, Eric Dumazet wrote: > From: Eric Dumazet > > TC_ACT_STOLEN is used when ingress traffic is mirred/redirected > to say ifb. > > Packet is not dropped, but consumed. > > Only TC_ACT_SHOT is a clear indication something went wrong. >

Re: [patch net-next] mlxsw: spectrum: Fix ordering in mlxsw_sp_fini

From: Jiri Pirko Date: Fri, 6 May 2016 22:20:59 +0200 > From: Jiri Pirko > > Fixes: 0f433fa0ec ("mlxsw: spectrum_buffers: Implement shared buffer > configuration") > Signed-off-by: Jiri Pirko Applied.

Re: [Intel-wired-lan] [PATCH] e1000e: prevent division by zero if TIMINCA is zero

Denys Vlasenko wrote: Users report that under VMWare, er32(TIMINCA) returns zero. This causes division by zero at init time as follows: ==>incvalue = er32(TIMINCA) & E1000_TIMINCA_INCVALUE_MASK; for (i = 0; i < E1000_MAX_82574_SYSTIM_REREADS;

Re: [PATCH 1/2] net: phy: add ethtool_phy_{get|set}_link_ksettings

On 06/05/16 16:18, Philippe Reynes wrote: > The callback {get|set}_link_ksettings are often defined > in a very close way. There are mainly two differences in > those callback: > - the name of the netdev private structure > - the name of the struct phydev in the private structure > > We add two

[PATCH net-next] ifb: support more features

From: Eric Dumazet When using ifb+netem on ingress on SIT/IPIP/GRE traffic, GRO packets are not properly processed. Segmentation should not be forced, as ifb is already adding quite a performance hit. Signed-off-by: Eric Dumazet --- drivers/net/ifb.c

[PATCH 2/2] net: ethernet: fec: use ethtool_phy_{get|set}_link_ksettings

Use the generic ethtool_phy_{get|set}_link_ksettings to generate the callback for {get|set}_link_ksettings. Signed-off-by: Philippe Reynes --- drivers/net/ethernet/freescale/fec_main.c | 25 ++--- 1 files changed, 2 insertions(+), 23 deletions(-) diff

[PATCH 1/2] net: phy: add ethtool_phy_{get|set}_link_ksettings

The callback {get|set}_link_ksettings are often defined in a very close way. There are mainly two differences in those callback: - the name of the netdev private structure - the name of the struct phydev in the private structure We add two defines ethtool_phy_{get|set}_link_ksettings to avoid

[PATCH net-next 3/7] Driver: Vmxnet3: Allow variable length Transmit Data ring buffer

Signed-off-by: Sriram Rangarajan Signed-off-by: Shrikrishna Khare --- drivers/net/vmxnet3/vmxnet3_defs.h| 12 +++- drivers/net/vmxnet3/vmxnet3_drv.c | 55 ++- drivers/net/vmxnet3/vmxnet3_ethtool.c | 9 +++---

[PATCH net-next 4/7] Driver: Vmxnet3: Add Receive Data Ring support

Receive Data Ring buffer length is configurable via ethtool -G ethX rx-mini Signed-off-by: Shrikrishna Khare --- drivers/net/vmxnet3/vmxnet3_defs.h| 14 +++- drivers/net/vmxnet3/vmxnet3_drv.c | 153 +++---

[PATCH net-next 0/7] Driver: Vmxnet3: Version 3

This patchset upgrades Vmxnet3 to Version 3. Shrikrishna Khare (7): Driver: Vmxnet3: Prepare for version 3 changes Driver: Vmxnet3: Introduce generic command interface to configure the device Driver: Vmxnet3: Allow variable length Transmit Data ring buffer Driver: Vmxnet3: Add

[PATCH net-next 2/7] Driver: Vmxnet3: Introduce generic command interface to configure the device

Signed-off-by: Guolin Yang Signed-off-by: Shrikrishna Khare --- drivers/net/vmxnet3/vmxnet3_defs.h | 22 +- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/drivers/net/vmxnet3/vmxnet3_defs.h

[PATCH net-next 5/7] Driver: Vmxnet3: Add support for get_coalesce, set_coalesce ethtool operations

Signed-off-by: Keyong Sun Signed-off-by: Manoj Tammali Signed-off-by: Shrikrishna Khare --- drivers/net/vmxnet3/vmxnet3_defs.h| 32 +++- drivers/net/vmxnet3/vmxnet3_drv.c | 47

[PATCH net-next 7/7] Driver: Vmxnet3: Update to Version 3

Signed-off-by: Shrikrishna Khare --- drivers/net/vmxnet3/vmxnet3_drv.c | 7 ++- drivers/net/vmxnet3/vmxnet3_int.h | 4 ++-- 2 files changed, 8 insertions(+), 3 deletions(-) diff --git a/drivers/net/vmxnet3/vmxnet3_drv.c b/drivers/net/vmxnet3/vmxnet3_drv.c index

[PATCH net-next 1/7] Driver: Vmxnet3: Prepare for version 3 changes

Signed-off-by: Shrikrishna Khare --- drivers/net/vmxnet3/Makefile | 4 ++-- drivers/net/vmxnet3/upt1_defs.h | 4 ++-- drivers/net/vmxnet3/vmxnet3_defs.h| 9 ++--- drivers/net/vmxnet3/vmxnet3_drv.c | 22 +-

[PATCH net-next 6/7] Driver: Vmxnet3: Introduce command to register memory region

Signed-off-by: Guolin Yang Signed-off-by: Shrikrishna Khare --- drivers/net/vmxnet3/vmxnet3_defs.h | 17 + 1 file changed, 17 insertions(+) diff --git a/drivers/net/vmxnet3/vmxnet3_defs.h b/drivers/net/vmxnet3/vmxnet3_defs.h index

Re: [RFC PATCH v3 00/19] CALIPSO Implementation

On Wed, Feb 17, 2016 at 8:21 AM, Huw Davies wrote: > This patch series implements RFC 5570 - Common Architecture Label IPv6 > Security Option (CALIPSO). Its goal is to set MLS sensitivity labels > on IPv6 packets using a hop-by-hop option. CALIPSO is very similar to > its

[PATCH 2/2] net: Use ns_capable_noaudit() when determining net sysctl permissions

The capability check should not be audited since it is only being used to determine the inode permissions. A failed check does not indicate a violation of security policy but, when an LSM is enabled, a denial audit message was being generated. The denial audit message caused confusion for some

[PATCH 1/2] kernel: Add noaudit variant of ns_capable()

When checking the current cred for a capability in a specific user namespace, it isn't always desirable to have the LSMs audit the check. This patch adds a noaudit variant of ns_capable() for when those situations arise. The common logic between ns_capable() and the new ns_capable_noaudit() is

[PATCH 0/2] Quiet noisy LSM denial when accessing net sysctl

This pair of patches does away with what I believe is a useless denial audit message when a privileged process initially accesses a net sysctl. The bug was first discovered when running Go applications under AppArmor confinement. It can be triggered like so: $ echo "profile test { file, }" |

Re: [RFC PATCH v3 17/19] calipso: Add validation of CALIPSO option.

On Wed, Feb 17, 2016 at 8:22 AM, Huw Davies wrote: > We check lengths, checksum and the DOI. We leave checking of the > level and categories for the socket layer. > > Signed-off-by: Huw Davies > --- > include/net/calipso.h | 6 ++ >

[PATCH net-next] net: make sch_handle_ingress() drop monitor ready

From: Eric Dumazet TC_ACT_STOLEN is used when ingress traffic is mirred/redirected to say ifb. Packet is not dropped, but consumed. Only TC_ACT_SHOT is a clear indication something went wrong. Signed-off-by: Eric Dumazet Cc: Jamal Hadi Salim

Re: [PATCH v3 net-next 02/11] net: define gso types for IPx over IPv4 and IPv6

On Fri, May 6, 2016 at 3:48 PM, Alexander Duyck wrote: > On 05/06/2016 03:11 PM, Tom Herbert wrote: >> >> This patch defines two new GDO definitions SKB_GSO_IPXIP4 and >> SKB_GSO_IPXIP6 along with corresponding NETIF_F_GSO_IPXIP4 and >> NETIF_F_GSO_IPXIP6. These are

Re: [PATCH v3 net-next 02/11] net: define gso types for IPx over IPv4 and IPv6

On 05/06/2016 03:11 PM, Tom Herbert wrote: This patch defines two new GDO definitions SKB_GSO_IPXIP4 and SKB_GSO_IPXIP6 along with corresponding NETIF_F_GSO_IPXIP4 and NETIF_F_GSO_IPXIP6. These are used to described IP in IP tunnel and what the outer protocol is. The inner protocol can be

Re: [PATCH v3 net-next 01/11] gso: Remove arbitrary checks for unsupported GSO

On 05/06/2016 03:11 PM, Tom Herbert wrote: In several gso_segment functions there are checks of gso_type against a seemingly arbitrary list of SKB_GSO_* flags. This seems like an attempt to identify unsupported GSO types, but since the stack is the one that set these GSO types in the first place

Re: [PATCH net-next 15/21] net: dsa: mv88e6xxx: factorize VLAN Ethertype

On Fri, May 06, 2016 at 05:57:17PM -0400, Vivien Didelot wrote: > The 6131 switch models have a Core Tag Type register. Add a > MV88E6XXX_FLAG_CORE_TAG_TYPE flag and set the VLAN Ethertype to 0x8100 > in the shared setup code if it is present. Do you have any idea what the core tag is? Andrew

Re: [patch net 0/2] mlxsw: Couple of fixes

From: Jiri Pirko Date: Fri, 6 May 2016 22:18:38 +0200 > From: Jiri Pirko > > Ido Schimmel (2): > mlxsw: spectrum: Fix rollback order in LAG join failure > mlxsw: spectrum: Add missing rollback in flood configuration Applied.

Re: [PATCH net-next 13/21] net: dsa: mv88e6xxx: factorize global setup

> > -int mv88e6xxx_setup_common(struct mv88e6xxx_priv_state *ps) > +static int _mv88e6xxx_setup_global(struct mv88e6xxx_priv_state *ps) Another _ prefix. Andrew

Re: [PATCH net-next 12/21] net: dsa: mv88e6xxx: factorize switch reset

> diff --git a/drivers/net/dsa/mv88e6xxx.c b/drivers/net/dsa/mv88e6xxx.c > index dbbda4e..b744ed5 100644 > --- a/drivers/net/dsa/mv88e6xxx.c > +++ b/drivers/net/dsa/mv88e6xxx.c > @@ -2551,6 +2551,68 @@ restore_page_0: > return ret; > } > > +static int _mv88e6xxx_switch_reset(struct

Re: [PATCH net v3 1/2] udp_tunnel: Remove redundant udp_tunnel_gro_complete().

From: Jarno Rajahalme Date: Tue, 3 May 2016 16:10:20 -0700 > The setting of the UDP tunnel GSO type is already performed by > udp[46]_gro_complete(). > > Signed-off-by: Jarno Rajahalme Applied.

Re: [PATCH net v3 2/2] udp_offload: Set encapsulation before inner completes.

From: Jarno Rajahalme Date: Tue, 3 May 2016 16:10:21 -0700 > UDP tunnel segmentation code relies on the inner offsets being set for > an UDP tunnel GSO packet, but the inner *_complete() functions will > set the inner offsets only if 'encapsulation' is set before calling > them.

Re: [PATCH net-next 06/21] net: dsa: mv88e6xxx: factorize MAC address setting

> @@ -378,6 +385,7 @@ enum mv88e6xxx_cap { > #define MV88E6XXX_FLAG_EEPROMBIT(MV88E6XXX_CAP_EEPROM) > #define MV88E6XXX_FLAG_PPU BIT(MV88E6XXX_CAP_PPU) > #define MV88E6XXX_FLAG_SMI_PHY BIT(MV88E6XXX_CAP_SMI_PHY) > +#define MV88E6XXX_FLAG_SWITCH_MAC

Re: [PATCHv2 bluetooth-next 04/10] ndisc: add addr_len parameter to ndisc_opt_addr_space

On 04.05.2016 14:30, Alexander Aring wrote: > Hi, > > On 05/02/2016 09:37 PM, Hannes Frederic Sowa wrote: >> On 20.04.2016 10:19, Alexander Aring wrote: >>> This patch makes the address length as argument for the >>> ndisc_opt_addr_space function. This is necessary to handle addresses >>> which

Re: [PATCH net-next 04/21] net: dsa: mv88e6xxx: factorize EEPROM access

> @@ -2596,6 +2797,9 @@ int mv88e6xxx_setup_common(struct mv88e6xxx_priv_state > *ps) > > INIT_WORK(>bridge_work, mv88e6xxx_bridge_work); > > + if (mv88e6xxx_has(ps, MV88E6XXX_FLAG_EEPROM)) > + mutex_init(>eeprom_mutex); > + This seems to be the only place

[PATCH v3 net-next 01/11] gso: Remove arbitrary checks for unsupported GSO

In several gso_segment functions there are checks of gso_type against a seemingly arbitrary list of SKB_GSO_* flags. This seems like an attempt to identify unsupported GSO types, but since the stack is the one that set these GSO types in the first place this seems unnecessary to do. If a

[PATCH v3 net-next 03/11] gre6: Fix flag translations

GRE for IPv6 does not properly translate for GRE flags to tunnel flags and vice versa. This patch fixes that. Signed-off-by: Tom Herbert --- net/ipv6/ip6_gre.c | 20 1 file changed, 12 insertions(+), 8 deletions(-) diff --git a/net/ipv6/ip6_gre.c

[PATCH v3 net-next 05/11] fou: Split out {fou,gue}_build_header

Create __fou_build_header and __gue_build_header. These implement the protocol generic parts of building the fou and gue header. fou_build_header and gue_build_header implement the IPv4 specific functions and call the __*_build_header functions. Signed-off-by: Tom Herbert

[PATCH v3 net-next 06/11] fou: Add encap ops for IPv6 tunnels

Thsi packet adds IP tunnel encapsulation operations for IPv6. This includes the infrastructure to add and delete operations. IPv6 variants for fou6_build_header and gue6_build_header are added in a new fou6 module. These encapsulation operations for fou and gue are automatically added when the

[PATCH v3 net-next 02/11] net: define gso types for IPx over IPv4 and IPv6

This patch defines two new GDO definitions SKB_GSO_IPXIP4 and SKB_GSO_IPXIP6 along with corresponding NETIF_F_GSO_IPXIP4 and NETIF_F_GSO_IPXIP6. These are used to described IP in IP tunnel and what the outer protocol is. The inner protocol can be deduced from other GSO types (e.g. SKB_GSO_TCPV4

[PATCH v3 net-next 11/11] ip6_gre: Add support for fou/gue encapsulation

Add netlink and setup for encapsulation Signed-off-by: Tom Herbert --- net/ipv6/ip6_gre.c | 75 ++ 1 file changed, 75 insertions(+) diff --git a/net/ipv6/ip6_gre.c b/net/ipv6/ip6_gre.c index 70a1f72..ed5ddcc 100644 ---

[PATCH v3 net-next 08/11] ipv6: Change "final" protocol processing for encapsulation

When performing foo-over-UDP, UDP are receveived processed by the encapsulation header which returns another protocol to process. This may result in processing two (or more) protocols in the loop that are marked as INET6_PROTO_FINAL. The actions taken for hitting a final protocol, in particular

[PATCH v3 net-next 00/11] ipv6: Enable GUEoIPv6 and more fixes for v6 tunneling

This patch set: - Fixes GRE6 to process translate flags correctly from configuration - Adds support for GSO and GRO for ip6ip6 and ip4ip6 - Add support for FOU and GUE in IPv6 - Support GRE, ip6ip6 and ip4ip6 over FOU/GUE - Fixes ip6_input to deal with UDP encapsulations - Some other

[PATCH v3 net-next 09/11] fou: Support IPv6 in fou

This patch adds receive path support for IPv6 with fou. - Add address family to fou structure for open sockets. This supports AF_INET and AF_INET6. Lookups for fou ports are performed on both the port number and family. - In fou and gue receive adjust tot_len in IPv4 header or payload_len

[PATCH v3 net-next 04/11] fou: Call setup_udp_tunnel_sock

Use helper function to set up UDP tunnel related information for a fou socket. Signed-off-by: Tom Herbert --- net/ipv4/fou.c | 50 -- 1 file changed, 16 insertions(+), 34 deletions(-) diff --git a/net/ipv4/fou.c

[PATCH v3 net-next 10/11] ip6_tun: Add infrastructure for doing encapsulation

Add encap_hlen and ip_tunnel_encap structure to ip6_tnl. Add functions for getting encap hlen, setting up encap on a tunnel, performing encapsulation operation. Signed-off-by: Tom Herbert --- include/net/ip6_tunnel.h | 8 +- net/ipv6/ip6_tunnel.c | 4 +++

[PATCH v3 net-next 07/11] ipv6: Fix nexthdr for reinjection

In ip6_input_finish the protocol handle returns a value greater than zero the packet needs to be resubmitted using the returned protocol. The returned protocol is being ignored and each time through resubmit nexthdr is taken from an offest in the packet. This patch fixes that so that nexthdr is

[PATCH net-next 08/21] net: dsa: mv88e6xxx: factorize registers access

Only 6131 was not supporting the port registers access yet. Assume such support and use the unlock access routines in the meantime. Signed-off-by: Vivien Didelot --- drivers/net/dsa/mv88e6131.c | 2 ++ drivers/net/dsa/mv88e6xxx.c | 6 +- 2 files changed,

[PATCH net-next 00/21] net: dsa: mv88e6xxx: turn into monolithic driver

This patchset merges all mv88e6* drivers supported by the shared mv88e6xxx code into a single mv88e6xxx DSA switch driver. Some flags are added to describe the capabilities of a switch model, such as the presence of a PPU, EEPROM, some old or new registers, etc. First these flags are used to

[PATCH net-next 07/21] net: dsa: mv88e6xxx: factorize EEE access

Add a MV88E6XXX_FLAG_EEE flag to describe switch models featuring Energy Efficient Ethernet. Use it to conditionally support such access in the common code. Signed-off-by: Vivien Didelot --- drivers/net/dsa/mv88e6123.c | 2 ++ drivers/net/dsa/mv88e6131.c |

[PATCH net-next 01/21] net: dsa: mv88e6xxx: add flags to info

Add a flags bitmap to the info structure in order to identify features supported or not by the different switch models. Signed-off-by: Vivien Didelot --- drivers/net/dsa/mv88e6123.c | 3 +++ drivers/net/dsa/mv88e6131.c | 4 drivers/net/dsa/mv88e6171.c

[PATCH net-next 04/21] net: dsa: mv88e6xxx: factorize EEPROM access

Add a MV88E6XXX_FLAG_EEPROM flag to describe switch models featuring an EEPROM and distribute the EEPROM access routines to all models. Signed-off-by: Vivien Didelot --- drivers/net/dsa/mv88e6123.c | 2 + drivers/net/dsa/mv88e6131.c | 2 +

[PATCH net-next 09/21] net: dsa: mv88e6xxx: factorize bridge support

Add MV88E6XXX_FLAG_PORTSTATE and MV88E6XXX_FLAG_VLANTABLE flags to identify switch models with required 802.1D operations. Signed-off-by: Vivien Didelot --- drivers/net/dsa/mv88e6123.c | 3 +++ drivers/net/dsa/mv88e6131.c | 1 + drivers/net/dsa/mv88e6xxx.c

[PATCH net-next 03/21] net: dsa: mv88e6xxx: factorize PHY indirect access

Some switch has dedicated SMI PHY Command and Data registers, used to indirectly access the PHYs, instead of direct access. Identify these switch models and make mv88e6xxx_phy_{read,write} generic enough to support every models. Signed-off-by: Vivien Didelot

Re: rtk8168 driver help needed

On 05/06/2016 06:02 PM, Murali Karicheri wrote: > Hi, > > I am trying to integrate the rtl8168 PCIe card to have Ethernet functional on > my > Keystone EVM. I purchased the rtl8111c Gib card from Amazon. The Card is > detected > by the RC and I can see it is enumerated and show up when doing

[PATCH net-next 10/21] net: dsa: mv88e6xxx: factorize VTU access

Add a MV88E6XXX_FLAG_VTU flag to indentify switch models with a VLAN Table Unit. Signed-off-by: Vivien Didelot --- drivers/net/dsa/mv88e6123.c | 5 + drivers/net/dsa/mv88e6xxx.c | 16 drivers/net/dsa/mv88e6xxx.h | 24

[PATCH net-next 15/21] net: dsa: mv88e6xxx: factorize VLAN Ethertype

The 6131 switch models have a Core Tag Type register. Add a MV88E6XXX_FLAG_CORE_TAG_TYPE flag and set the VLAN Ethertype to 0x8100 in the shared setup code if it is present. Signed-off-by: Vivien Didelot --- drivers/net/dsa/mv88e6131.c | 5 -

rtk8168 driver help needed

Hi, I am trying to integrate the rtl8168 PCIe card to have Ethernet functional on my Keystone EVM. I purchased the rtl8111c Gib card from Amazon. The Card is detected by the RC and I can see it is enumerated and show up when doing lspci command. However I can't get the Ethernet port functional.

[PATCH net-next 02/21] net: dsa: mv88e6xxx: factorize PHY access with PPU

Add a MV88E6XXX_FLAG_PPU flag to describe switch models with a PHY Polling Unit. This allows to merge PPU specific PHY access code in the share code. Make the mv88e6xxx_ppu_disable and mv88e6xxx_phy_{read,write}_ppu functions use unlocked register accesses in order to call them in

[PATCH net-next 05/21] net: dsa: mv88e6xxx: factorize temperature access

Add MV88E6XXX_FLAG_TEMP and MV88E6XXX_FLAG_TEMP_LIMIT flags to describe switch models featuring a temperature access. Use them to centralize the access to the temperature feature. Signed-off-by: Vivien Didelot --- drivers/net/dsa/mv88e6123.c | 3 +++

[PATCH net-next 06/21] net: dsa: mv88e6xxx: factorize MAC address setting

Some switch models have a dedicated register for Switch MAC/WoF/WoL. This register, when present, is used to indirectly set the switch MAC address, instead of a direct write to 3 global registers. Identify this feature and share a common mv88e6xxx_set_addr function. Signed-off-by: Vivien Didelot

[PATCH net-next 21/21] net: dsa: mv88e6xxx: factorize the switch driver

Now that all drivers support the same set of functions and the same setup code, drop every model-specific DSA switch driver and replace them with a common mv88e6xxx driver. This merges the info tables into one, removes the function exports, the model-specific files, and update the defconfigs.

[PATCH net-next 19/21] net: dsa: mv88e6xxx: factorize switch setup

Provide a shared mv88e6xxx_setup function to the drivers. Signed-off-by: Vivien Didelot --- drivers/net/dsa/mv88e6123.c | 16 +-- drivers/net/dsa/mv88e6131.c | 16 +-- drivers/net/dsa/mv88e6171.c | 16 +-- drivers/net/dsa/mv88e6352.c

[PATCH net-next 16/21] net: dsa: mv88e6xxx: factorize GLOBAL_MONITOR_CONTROL setup

All switch drivers configure the GLOBAL_MONITOR_CONTROL register with slightly changes. Assume the setup of the upstream port, and configure it as the port to which ingress and egress and ARP monitor frames are to be sent. Signed-off-by: Vivien Didelot ---

[PATCH net-next 11/21] net: dsa: mv88e6xxx: factorize ATU access

Add a MV88E6XXX_FLAG_ATU flag to identify switch models with an Address Translation Unit. Signed-off-by: Vivien Didelot --- drivers/net/dsa/mv88e6123.c | 4 drivers/net/dsa/mv88e6xxx.c | 14 ++ drivers/net/dsa/mv88e6xxx.h | 24

[PATCH net-next 13/21] net: dsa: mv88e6xxx: factorize global setup

Every driver is calling mv88e6xxx_setup_global after mv88e6xxx_setup_common. Call the former in the latter. Signed-off-by: Vivien Didelot --- drivers/net/dsa/mv88e6123.c | 4 -- drivers/net/dsa/mv88e6131.c | 4 -- drivers/net/dsa/mv88e6171.c | 4 --

[PATCH net-next 17/21] net: dsa: mv88e6xxx: factorize GLOBAL_CONTROL_2 setup

All switch models setup the GLOBAL_CONTROL_2 register with slightly differences. Since the cascade mode is valid even in a single chip setup, factorize such configuration. Signed-off-by: Vivien Didelot --- drivers/net/dsa/mv88e6123.c | 15 ---

[PATCH net-next 14/21] net: dsa: mv88e6xxx: factorize GLOBAL_CONTROL setup

All switch models configure the GLOBAL_CONTROL register with slightly differences. Discarding packets with excessive collisions (GLOBAL_CONTROL_DISCARD_EXCESS) is specific to 6352 and similar switches, and setting a maximum frame size (GLOBAL_CONTROL_MAX_FRAME_1632) is specific to 6185 and

[PATCH net-next 12/21] net: dsa: mv88e6xxx: factorize switch reset

Add a MV88E6XXX_FLAG_PPU_ACTIVE flag to describe how to reset the switch, and merge the reset call to the common setup code. Signed-off-by: Vivien Didelot --- drivers/net/dsa/mv88e6123.c | 4 -- drivers/net/dsa/mv88e6131.c | 4 --

[PATCH net-next 18/21] net: dsa: mv88e6xxx: factorize frames priorities

6131 is the only driver to setup the priority of IGMP/MLD snoop frames and ARP frames to the highest setting. Drop such change until we figure out a common configuration for all switch models. Signed-off-by: Vivien Didelot --- drivers/net/dsa/mv88e6131.c |

[PATCH net-next 20/21] net: dsa: mv88e6xxx: factorize tag protocol

6131 is the only driver to set the tag protocol to DSA_TAG_PROTO_DSA. Since it works fine with DSA_TAG_PROTO_EDSA, change its value, like all other mv88e6xxx drivers. Signed-off-by: Vivien Didelot --- drivers/net/dsa/Kconfig | 2 +-

Re: [REGRESSION] asix: Lots of asix_rx_fixup() errors and slow transmissions

On Tue, May 3, 2016 at 2:16 PM, Dean Jenkins wrote: > > [ 239.027993] asix 1-1.1:1.0 eth0: asix_rx_fixup() Data Header > synchronisation was lost, remaining 988 > > This error message consistently shows the remaining value to be 988, at > least for the 3 examples

Re: [RFC PATCH net-next 19/20] net: dsa: mv88e6xxx: factorize tag protocol

Hi Andrew, Andrew Lunn writes: > On Thu, May 05, 2016 at 06:41:03PM -0400, Vivien Didelot wrote: >> 6131 is the only driver to set the tag protocol to DSA_TAG_PROTO_DSA. >> Since it works fine with DSA_TAG_PROTO_EDSA, change its value, like all >> other mv88e6xxx drivers. > >

Re: [PATCH v2 next-next 02/12] net: define gso types for IPx over IPv4 and IPv6

On Fri, May 6, 2016 at 1:43 PM, Tom Herbert wrote: > On Fri, May 6, 2016 at 1:34 PM, Alexander Duyck > wrote: >> On Fri, May 6, 2016 at 1:04 PM, Tom Herbert wrote: >>> This patch defines two new GDO definitions

Re: [REGRESSION] asix: Lots of asix_rx_fixup() errors and slow transmissions

On 2016-05-04 03:58, Dean Jenkins wrote: On 04/05/16 01:28, David B. Robins wrote: Here is the code snippet from the patch with my annotations between # #, I will try to explain my intentions. Feel free to point out any flaws: if (rx->remaining && (rx->remaining + sizeof(u32) <=

Re: [PATCH v2 next-next 02/12] net: define gso types for IPx over IPv4 and IPv6

On Fri, May 6, 2016 at 1:34 PM, Alexander Duyck wrote: > On Fri, May 6, 2016 at 1:04 PM, Tom Herbert wrote: >> This patch defines two new GDO definitions SKB_GSO_IPXIP4 and >> SKB_GSO_IPXIP6 along with corresponding NETIF_F_GSO_IPXIP4 and >>

Re: [PATCH] netdev: enc28j60 kernel panic fix.

(please don't top post) David Russell : > I kind of thought my patch was at best incomplete. When you state > this change silences the bug but does not fix it, what are the > implications of systems running this patch? We have some production > systems using this patch.

Re: [PATCH v2 next-next 02/12] net: define gso types for IPx over IPv4 and IPv6

On Fri, May 6, 2016 at 1:04 PM, Tom Herbert wrote: > This patch defines two new GDO definitions SKB_GSO_IPXIP4 and > SKB_GSO_IPXIP6 along with corresponding NETIF_F_GSO_IPXIP4 and > NETIF_F_GSO_IPXIP6. These are used to described IP in IP > tunnel and what the outer protocol

Re: [PATCH v2 next-next 04/12] udp: Don't set skb->encapsulation with RCO

On Fri, May 6, 2016 at 1:04 PM, Tom Herbert wrote: > When RCO is in effect we want to ensure that the outer checksum is > properly offloaded. Don't set skb->encapsulation in this case to > ensure that checksum offload is later considered for hw_features > instead of

[patch net-next] mlxsw: spectrum: Fix ordering in mlxsw_sp_fini

From: Jiri Pirko Fixes: 0f433fa0ec ("mlxsw: spectrum_buffers: Implement shared buffer configuration") Signed-off-by: Jiri Pirko --- drivers/net/ethernet/mellanox/mlxsw/spectrum.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [PATCH net v3 2/2] udp_offload: Set encapsulation before inner completes.

On Fri, May 6, 2016 at 12:34 PM, David Miller wrote: > From: Jarno Rajahalme > Date: Tue, 3 May 2016 16:10:21 -0700 > >> UDP tunnel segmentation code relies on the inner offsets being set for >> an UDP tunnel GSO packet, but the inner *_complete() functions

[patch net 2/2] mlxsw: spectrum: Add missing rollback in flood configuration

From: Ido Schimmel When we fail to set the flooding configuration for the broadcast and unregistered multicast traffic, we should revert the flooding configuration of the unknown unicast traffic. Fixes: 0293038e0c36 ("mlxsw: spectrum: Add support for flood control")

[patch net 0/2] mlxsw: Couple of fixes

From: Jiri Pirko Ido Schimmel (2): mlxsw: spectrum: Fix rollback order in LAG join failure mlxsw: spectrum: Add missing rollback in flood configuration drivers/net/ethernet/mellanox/mlxsw/spectrum.c | 4 ++--

[patch net 1/2] mlxsw: spectrum: Fix rollback order in LAG join failure

From: Ido Schimmel Make the leave procedure in the error path symmetric to the join procedure and first remove the port from the collector before potentially destroying the LAG. Fixes: 0d65fc13042f ("mlxsw: spectrum: Implement LAG port join/leave") Signed-off-by: Ido

Re: [patch net 0/3] mlxsw: Couple of fixes

From: Jiri Pirko Date: Fri, 6 May 2016 22:13:49 +0200 > Fri, May 06, 2016 at 10:00:32PM CEST, da...@davemloft.net wrote: >>From: Jiri Pirko >>Date: Fri, 6 May 2016 11:17:21 +0200 >> >>> From: Jiri Pirko >>> >>> Ido Schimmel (2): >>>

Re: [patch net 0/3] mlxsw: Couple of fixes

Fri, May 06, 2016 at 10:00:32PM CEST, da...@davemloft.net wrote: >From: Jiri Pirko >Date: Fri, 6 May 2016 11:17:21 +0200 > >> From: Jiri Pirko >> >> Ido Schimmel (2): >> mlxsw: spectrum: Fix rollback order in LAG join failure >> mlxsw: spectrum: Add

Re: [PATCH 2/3] net/mlx5e: make VXLAN support conditional

On Thu, May 5, 2016 at 11:09 AM, Arnd Bergmann wrote: > On Thursday 05 May 2016 19:44:36 Saeed Mahameed wrote: >> On Wed, May 4, 2016 at 3:31 PM, Arnd Bergmann wrote: >> > VXLAN can be disabled at compile-time or it can be a loadable >> > module while mlx5 is

  1   2   3   >