# Conflicts:
#	MAINTAINERS
This commit is contained in:
Mark Brown
2026-07-31 14:50:45 +01:00
645 changed files with 68013 additions and 13763 deletions
@@ -0,0 +1,71 @@
# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
%YAML 1.2
---
$id: http://devicetree.org/schemas/net/adi,ad3306.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#
title: ADI ADIN1140 10BASE-T1S MAC-PHY
maintainers:
- Ciprian Regus <ciprian.regus@analog.com>
description: |
The ADIN1140 (also called AD3306) is a low power single port
10BASE-T1S MAC-PHY. It integrates an Ethernet PHY with a MAC
and all the associated analog circuitry.
The device tries to implement the Open Alliance TC6 10BASE-T1x MAC-PHY
Serial Interface specification and is compliant with the
IEEE 802.3cg-2019 Ethernet standard for 10 Mbps single pair
Ethernet (SPE). The device has a 4-wire SPI interface for
communication between the MAC and host processor.
allOf:
- $ref: /schemas/net/ethernet-controller.yaml#
- $ref: /schemas/spi/spi-peripheral-props.yaml#
properties:
compatible:
oneOf:
- items:
- const: adi,adin1140
- const: adi,ad3306
- const: adi,ad3306
reg:
maxItems: 1
spi-max-frequency:
maximum: 25000000
interrupts:
maxItems: 1
description: Interrupt from the MAC-PHY for receive data available
and error conditions
required:
- compatible
- reg
- interrupts
- spi-max-frequency
unevaluatedProperties: false
examples:
- |
#include <dt-bindings/interrupt-controller/irq.h>
spi {
#address-cells = <1>;
#size-cells = <0>;
ethernet@0 {
compatible = "adi,ad3306";
reg = <0>;
spi-max-frequency = <23000000>;
interrupt-parent = <&gpio>;
interrupts = <6 IRQ_TYPE_LEVEL_LOW>;
local-mac-address = [ 00 11 22 33 44 55 ];
};
};
@@ -100,6 +100,10 @@ properties:
Built-in switch of the Airoha AN7583 SoC
const: airoha,an7583-switch
- description:
Built-in switch of the EcoNet EN7528 SoC
const: econet,en7528-switch
reg:
maxItems: 1
@@ -318,6 +322,7 @@ allOf:
- mediatek,mt7988-switch
- airoha,en7581-switch
- airoha,an7583-switch
- econet,en7528-switch
then:
$ref: "#/$defs/builtin-dsa-port"
properties:
@@ -20,16 +20,37 @@ select:
contains:
enum:
- eswin,eic7700-qos-eth
- eswin,eic7700-qos-eth-clk-inversion
required:
- compatible
allOf:
- $ref: snps,dwmac.yaml#
- if:
properties:
compatible:
contains:
const: eswin,eic7700-qos-eth
then:
properties:
tx-internal-delay-ps:
maximum: 2540
- if:
properties:
compatible:
contains:
const: eswin,eic7700-qos-eth-clk-inversion
then:
properties:
tx-internal-delay-ps:
minimum: 2000
properties:
compatible:
items:
- const: eswin,eic7700-qos-eth
- enum:
- eswin,eic7700-qos-eth
- eswin,eic7700-qos-eth-clk-inversion
- const: snps,dwmac-5.20
reg:
@@ -63,10 +84,14 @@ properties:
- const: stmmaceth
rx-internal-delay-ps:
enum: [0, 200, 600, 1200, 1600, 1800, 2000, 2200, 2400]
minimum: 0
maximum: 2540
multipleOf: 20
tx-internal-delay-ps:
enum: [0, 200, 600, 1200, 1600, 1800, 2000, 2200, 2400]
minimum: 0
maximum: 4540
multipleOf: 20
eswin,hsp-sp-csr:
description:
@@ -105,8 +130,6 @@ required:
- phy-mode
- resets
- reset-names
- rx-internal-delay-ps
- tx-internal-delay-ps
- eswin,hsp-sp-csr
unevaluatedProperties: false
@@ -116,26 +139,51 @@ examples:
ethernet@50400000 {
compatible = "eswin,eic7700-qos-eth", "snps,dwmac-5.20";
reg = <0x50400000 0x10000>;
clocks = <&d0_clock 186>, <&d0_clock 171>, <&d0_clock 40>,
<&d0_clock 193>;
clock-names = "axi", "cfg", "stmmaceth", "tx";
interrupt-parent = <&plic>;
interrupts = <61>;
interrupt-names = "macirq";
phy-mode = "rgmii-id";
phy-handle = <&phy0>;
clocks = <&d0_clock 186>, <&d0_clock 171>, <&d0_clock 40>,
<&d0_clock 193>;
clock-names = "axi", "cfg", "stmmaceth", "tx";
resets = <&reset 95>;
reset-names = "stmmaceth";
rx-internal-delay-ps = <200>;
tx-internal-delay-ps = <200>;
eswin,hsp-sp-csr = <&hsp_sp_csr 0x100 0x108 0x118 0x114 0x11c>;
snps,axi-config = <&stmmac_axi_setup>;
phy-handle = <&phy0>;
phy-mode = "rgmii-id";
snps,aal;
snps,fixed-burst;
snps,tso;
snps,axi-config = <&stmmac_axi_setup>;
stmmac_axi_setup: stmmac-axi-config {
snps,blen = <0 0 0 0 16 8 4>;
snps,rd_osr_lmt = <2>;
snps,wr_osr_lmt = <2>;
};
};
ethernet@50410000 {
compatible = "eswin,eic7700-qos-eth-clk-inversion", "snps,dwmac-5.20";
reg = <0x50410000 0x10000>;
interrupt-parent = <&plic>;
interrupts = <70>;
interrupt-names = "macirq";
clocks = <&d0_clock 186>, <&d0_clock 171>, <&d0_clock 40>,
<&d0_clock 194>;
clock-names = "axi", "cfg", "stmmaceth", "tx";
resets = <&reset 94>;
reset-names = "stmmaceth";
eswin,hsp-sp-csr = <&hsp_sp_csr 0x200 0x208 0x218 0x214 0x21c>;
phy-handle = <&gmac1_phy0>;
phy-mode = "rgmii-id";
snps,aal;
snps,fixed-burst;
snps,tso;
snps,axi-config = <&stmmac_axi_setup_gmac1>;
stmmac_axi_setup_gmac1: stmmac-axi-config {
snps,blen = <0 0 0 0 16 8 4>;
snps,rd_osr_lmt = <2>;
snps,wr_osr_lmt = <2>;
};
};
@@ -0,0 +1,89 @@
# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
%YAML 1.2
---
$id: http://devicetree.org/schemas/net/microchip,lan7800.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#
title: Microchip LAN7800/LAN7801/LAN7850 Gigabit Ethernet controller
maintainers:
- Thangaraj Samynathan <Thangaraj.S@microchip.com>
- Rengarajan Sundararajan <Rengarajan.S@microchip.com>
description:
The LAN7800/LAN7801/LAN7850 devices are usually configured by
programming their OTP or with an external EEPROM, but some
platforms (e.g. Raspberry Pi 3 B+) have neither. The Device Tree
properties, if present, override the OTP and EEPROM.
allOf:
- $ref: /schemas/usb/usb-device.yaml#
- $ref: /schemas/net/ethernet-controller.yaml#
properties:
compatible:
enum:
- usb424,7800
- usb424,7801
- usb424,7850
reg:
maxItems: 1
description: USB port number
mdio:
$ref: /schemas/net/mdio.yaml#
unevaluatedProperties: false
patternProperties:
"^ethernet-phy(@[0-9a-f]+)?$":
$ref: /schemas/net/ethernet-phy.yaml#
unevaluatedProperties: false
type: object
properties:
microchip,led-modes:
$ref: /schemas/types.yaml#/definitions/uint32-array
minItems: 1
maxItems: 4
description:
Array of LED mode values for each of up to 4 LEDs.
Omitted LEDs are turned off. Allowed values are defined
in include/dt-bindings/net/microchip-lan78xx.h.
required:
- reg
required:
- compatible
- reg
unevaluatedProperties: false
examples:
- |
#include <dt-bindings/net/microchip-lan78xx.h>
usb {
#address-cells = <1>;
#size-cells = <0>;
ethernet@1 {
compatible = "usb424,7800";
reg = <1>;
local-mac-address = [00 11 22 33 44 55];
mdio {
#address-cells = <1>;
#size-cells = <0>;
ethernet-phy@1 {
reg = <1>;
microchip,led-modes = <
LAN78XX_LINK_1000_ACTIVITY
LAN78XX_LINK_10_100_ACTIVITY
>;
};
};
};
};
...
@@ -1,53 +0,0 @@
Microchip LAN78xx Gigabit Ethernet controller
The LAN78XX devices are usually configured by programming their OTP or with
an external EEPROM, but some platforms (e.g. Raspberry Pi 3 B+) have neither.
The Device Tree properties, if present, override the OTP and EEPROM.
Required properties:
- compatible: Should be one of "usb424,7800", "usb424,7801" or "usb424,7850".
The MAC address will be determined using the optional properties
defined in ethernet.txt.
Optional properties of the embedded PHY:
- microchip,led-modes: a 0..4 element vector, with each element configuring
the operating mode of an LED. Omitted LEDs are turned off. Allowed values
are defined in "include/dt-bindings/net/microchip-lan78xx.h".
Example:
/* Based on the configuration for a Raspberry Pi 3 B+ */
&usb {
usb-port@1 {
compatible = "usb424,2514";
reg = <1>;
#address-cells = <1>;
#size-cells = <0>;
usb-port@1 {
compatible = "usb424,2514";
reg = <1>;
#address-cells = <1>;
#size-cells = <0>;
ethernet: ethernet@1 {
compatible = "usb424,7800";
reg = <1>;
local-mac-address = [ 00 11 22 33 44 55 ];
mdio {
#address-cells = <0x1>;
#size-cells = <0x0>;
eth_phy: ethernet-phy@1 {
reg = <1>;
microchip,led-modes = <
LAN78XX_LINK_1000_ACTIVITY
LAN78XX_LINK_10_100_ACTIVITY
>;
};
};
};
};
};
};
@@ -35,7 +35,7 @@ properties:
- usb424,9906 # SMSC9505A USB Ethernet Device (HAL)
- usb424,9907 # SMSC9500 USB Ethernet Device (Alternate ID)
- usb424,9908 # SMSC9500A USB Ethernet Device (Alternate ID)
- usb424,9909 # SMSC9512/9514 USB Hub & Ethernet Device ID)
- usb424,9909 # SMSC9512/9514 USB Hub & Ethernet Device
- usb424,9e00 # SMSC9500A USB Ethernet Device
- usb424,9e01 # SMSC9505A USB Ethernet Device
- usb424,9e08 # SMSC LAN89530 USB Ethernet Device
+7
View File
@@ -91,6 +91,13 @@ following pin states:
- ``DPLL_PIN_STATE_DISCONNECTED`` - the pin shall be not considered as
a valid input for automatic selection algorithm
Pins that have the ``DPLL_PIN_CAPABILITIES_STATE_CONNECTED_OVERRIDE``
capability can additionally be set to ``DPLL_PIN_STATE_CONNECTED`` in
automatic mode, overriding the active input selection. This is useful
for automatic-only DPLL devices where mode cannot be switched to manual.
When such a pin is disconnected, the device returns to automatic input
selection.
The actual hardware status of a pin is reported via the operational
state (``DPLL_A_PIN_OPERSTATE``) attribute nested under the parent
device:
+26 -4
View File
@@ -895,6 +895,16 @@ attribute-sets:
resource-dump response. Bit 0 (dev) selects device-level
resources; bit 1 (port) selects port-level resources.
When absent all classes are returned.
-
name: parent-dev
type: nest
nested-attributes: dl-parent-dev
doc: |
Identifies the devlink instance which owns the parent rate node.
Used with rate-set and rate-new to parent a rate object to a node on
a different devlink instance, enabling cross-device rate scheduling.
When absent, the parent node is resolved on the same instance.
-
name: dl-dev-stats
subset-of: devlink
@@ -1317,6 +1327,16 @@ attribute-sets:
Specifies the bandwidth share assigned to the Traffic Class.
The bandwidth for the traffic class is determined
in proportion to the sum of the shares of all configured classes.
-
name: dl-parent-dev
subset-of: devlink
attributes:
-
name: bus-name
-
name: dev-name
-
name: index
operations:
enum-model: directional
@@ -2289,8 +2309,8 @@ operations:
dont-validate: [strict]
flags: [admin-perm]
do:
pre: devlink-nl-pre-doit
post: devlink-nl-post-doit
pre: devlink-nl-pre-doit-parent-dev-optional
post: devlink-nl-post-doit-parent-dev-optional
request:
attributes:
- bus-name
@@ -2303,6 +2323,7 @@ operations:
- rate-tx-weight
- rate-parent-node-name
- rate-tc-bws
- parent-dev
-
name: rate-new
@@ -2311,8 +2332,8 @@ operations:
dont-validate: [strict]
flags: [admin-perm]
do:
pre: devlink-nl-pre-doit
post: devlink-nl-post-doit
pre: devlink-nl-pre-doit-parent-dev-optional
post: devlink-nl-post-doit-parent-dev-optional
request:
attributes:
- bus-name
@@ -2325,6 +2346,7 @@ operations:
- rate-tx-weight
- rate-parent-node-name
- rate-tc-bws
- parent-dev
-
name: rate-del
+19
View File
@@ -165,6 +165,13 @@ definitions:
-
name: gnss
doc: GNSS recovered clock
-
name: int-nco
doc: |
Device internal numerically controlled oscillator.
When connected as a DPLL input, the DPLL enters NCO mode
where the output frequency is adjusted by the host via
the PTP clock interface.
render-max: true
-
type: enum
@@ -252,6 +259,12 @@ definitions:
-
name: state-can-change
doc: pin state can be changed
-
name: state-connected-override
doc: |
pin state can be set to connected regardless of current
DPLL device mode, overriding the active input selection.
Requires state-can-change to be set as well.
-
type: const
name: phase-offset-divider
@@ -456,6 +469,9 @@ attribute-sets:
offset on the media associated with the pin. Inside
the pin-parent-device nest it represents the frequency
offset between the pin and its parent DPLL device.
For pins of type PIN_TYPE_INT_NCO this represents
the DPLL's current output frequency offset from its
nominal frequency.
Value is in PPM (parts per million).
This is a lower-precision version of
fractional-frequency-offset-ppt.
@@ -502,6 +518,9 @@ attribute-sets:
offset on the media associated with the pin. Inside
the pin-parent-device nest it represents the frequency
offset between the pin and its parent DPLL device.
For pins of type PIN_TYPE_INT_NCO this represents
the DPLL's current output frequency offset from its
nominal frequency.
Value is in PPT (parts per trillion, 10^-12).
This is a higher-precision version of
fractional-frequency-offset.
+2 -2
View File
@@ -1139,10 +1139,10 @@ attribute-sets:
type: binary
-
name: fils-discovery
type: binary # TOOD: nest
type: binary # TODO: nest
-
name: unsol-bcast-probe-resp
type: binary # TOOD: nest
type: binary # TODO: nest
-
name: s1g-capability
type: binary
+4
View File
@@ -123,6 +123,9 @@ attribute-sets:
-
name: proto
type: u8
-
name: mc-users
type: u32
operations:
@@ -176,6 +179,7 @@ operations:
value: 58
attributes: &mcaddr-attrs
- multicast
- mc-users
- cacheinfo
dump:
request:
@@ -107,6 +107,15 @@ doesn't have the eswitch. Local controller (identified by controller number = 0)
has the eswitch. The Devlink instance on the local controller has eswitch
devlink ports for both the controllers.
A non-zero controller number may also be used for ports that are not external.
For example, a SmartNIC may have additional local PCI physical functions
that are managed by the eswitch but are not on an external host. These
ports use a non-zero controller number to distinguish them from the eswitch
manager's own functions, while the external flag remains unset.
The ``phys_port_name`` includes the controller prefix (``c<controller_num>``)
whenever the controller number is non-zero, regardless of the external flag.
Function configuration
======================
@@ -420,6 +429,8 @@ API allows to configure following rate object's parameters:
Parent node name. Parent node rate limits are considered as additional limits
to all node children limits. ``tx_max`` is an upper limit for children.
``tx_share`` is a total bandwidth distributed among children.
If the device supports cross-function scheduling, the parent can be from a
different function of the same underlying device.
``tc_bw``
Allow users to set the bandwidth allocation per traffic class on rate
+4 -4
View File
@@ -31,10 +31,10 @@ sure to respect following rules:
- Lock ordering should be maintained. If driver needs to take instance
lock of both nested and parent instances at the same time, devlink
instance lock of the parent instance should be taken first, only then
instance lock of the nested instance could be taken.
- Driver should use object-specific helpers to setup the nested relationship
before registering the nested devlink instance:
instance lock of the nested instance should be taken first, only then
instance lock of the parent instance could be taken.
- Driver should use object-specific helpers to setup the
nested relationship:
- ``devl_nested_devlink_set()`` - called to setup devlink -> nested
devlink relationship (could be used for multiple nested instances).
+33
View File
@@ -419,3 +419,36 @@ User commands examples:
.. note::
This command can run over all interfaces such as PF/VF and representor ports.
Rates
=====
mlx5 devices can limit transmission of individual VFs or a group of them via
the devlink-rate API in switchdev mode.
User commands examples:
- Print the existing rates::
$ devlink port function rate show
- Set a max tx limit on traffic from VF0::
$ devlink port function rate set pci/0000:82:00.0/1 tx_max 10Gbit
- Create a rate group with a max tx limit and add two VFs to it::
$ devlink port function rate add pci/0000:82:00.0/group1 tx_max 10Gbit
$ devlink port function rate set pci/0000:82:00.0/1 parent group1
$ devlink port function rate set pci/0000:82:00.0/2 parent group1
- Same scenario, with a min guarantee of 20% of the bandwidth for the first VF::
$ devlink port function rate add pci/0000:82:00.0/group1 tx_max 10Gbit
$ devlink port function rate set pci/0000:82:00.0/1 parent group1 tx_share 2Gbit
$ devlink port function rate set pci/0000:82:00.0/2 parent group1
- Cross-device scheduling::
$ devlink port function rate add pci/0000:82:00.0/group1 tx_max 10Gbit
$ devlink port function rate set pci/0000:82:00.1/32769 parent pci/0000:82:00.0/group1
@@ -22,6 +22,7 @@ struct_mutex ra_mutex
struct_fib_rules_ops* rules_ops
struct_fib_table fib_main
struct_fib_table fib_default
spinlock_t fib_table_hash_lock
unsigned_int fib_rules_require_fldissect
bool fib_has_custom_rules
bool fib_has_custom_local_routes
+7
View File
@@ -421,10 +421,17 @@ running under the lock:
* ``NETDEV_CHANGENAME``
* ``NETDEV_REGISTER``
* ``NETDEV_UP``
* ``NETDEV_DOWN``
* ``NETDEV_GOING_DOWN``
The following notifiers are running without the lock:
* ``NETDEV_UNREGISTER``
Many SW devices (uppers) catch their lower's ``NETDEV_UNREGISTER``
events and may interact with them via ``dev_*()`` handlers, which take
the instance lock. Until we convert these devices to ``netif_*()`` variants,
``NETDEV_UNREGISTER`` stays unlocked.
There are no clear expectations for the remaining notifiers. Notifiers not on
the list may run with or without the instance lock, potentially even invoking
the same notifier type with and without the lock from different code paths.
@@ -454,7 +454,8 @@ Device drivers API
The include/linux/oa_tc6.h defines the following functions:
.. c:function:: struct oa_tc6 *oa_tc6_init(struct spi_device *spi, \
struct net_device *netdev)
struct net_device *netdev, \
struct oa_tc6_quirks *quirks)
Initialize OA TC6 lib.
@@ -203,6 +203,22 @@ For RFC postings specifically, if nobody responded in a week - reviewers
either missed the posting or have no strong opinions. If the code is ready,
repost as a PATCH.
There are 2 services actively providing LLM-generated review on posted patches:
- https://sashiko.dev/
- https://netdev-ai.bots.linux.dev/sashiko/
both use the Sashiko infrastructure on top of different models. Reviews are
available after 24h. Patch authors are expected to proactively look into the
AI-generated reviews and handle such feedback as any other kind of review:
either debate it or address it. In both cases a reply on the mailing list is
expected.
Authors are strongly encouraged to run LLM reviews on the posted patches in
advance of the actual post. Large series triggering a significant amount of
AI-generated feedback will likely get little attention from maintainers and
reviewers.
Emails saying just "ping" or "bump" are considered rude. If you can't figure
out the status of the patch from patchwork or where the discussion has
landed - describe your best guess and ask if it's correct. For example::
@@ -210,6 +226,10 @@ landed - describe your best guess and ask if it's correct. For example::
I don't understand what the next steps are. Person X seems to be unhappy
with A, should I do B and repost the patches?
Don't reach out to maintainers or reviewers via private email and/or other
communications channels: all the discussion must remain public, and
requesting special attention is unfair towards the community, at best.
.. _Changes requested:
Changes requested
+31 -7
View File
@@ -1908,6 +1908,21 @@ S: Supported
W: https://ez.analog.com/linux-software-drivers
F: drivers/dma/dma-axi-dmac.c
ANALOG DEVICES INC ETHERNET DRIVERS
M: Ciprian Regus <ciprian.regus@analog.com>
L: netdev@vger.kernel.org
S: Maintained
W: https://ez.analog.com/linux-software-drivers
F: Documentation/devicetree/bindings/net/adi,ad3306.yaml
F: drivers/net/ethernet/adi/adin1140.c
ANALOG DEVICES INC ETHERNET PHY DRIVERS
M: Ciprian Regus <ciprian.regus@analog.com>
L: netdev@vger.kernel.org
S: Maintained
W: https://ez.analog.com/linux-software-drivers
F: drivers/net/phy/adin1140-phy.c
ANALOG DEVICES INC IIO DRIVERS
M: Nuno Sá <nuno.sa@analog.com>
M: Michael Hennerich <Michael.Hennerich@analog.com>
@@ -4263,7 +4278,6 @@ W: http://linux-atm.sourceforge.net
F: drivers/atm/
F: drivers/usb/atm/
F: include/linux/atm*
F: include/linux/sonet.h
F: include/uapi/linux/atm*
F: include/uapi/linux/sonet.h
F: net/atm/
@@ -9510,11 +9524,6 @@ L: linux-fbdev@vger.kernel.org
S: Maintained
F: drivers/video/fbdev/efifb.c
EHEA (IBM pSeries eHEA 10Gb ethernet adapter) DRIVER
L: netdev@vger.kernel.org
S: Orphan
F: drivers/net/ethernet/ibm/ehea/
ELM327 CAN NETWORK DRIVER
M: Max Staudt <max@enpas.org>
L: linux-can@vger.kernel.org
@@ -18229,6 +18238,14 @@ F: drivers/regulator/mpq7920.c
F: drivers/regulator/mpq7920.h
F: include/linux/mfd/mp2629.h
MORSE MICRO MM81X WIRELESS DRIVER
M: Lachlan Hodges <lachlan.hodges@morsemicro.com>
M: Dan Callaghan <dan.callaghan@morsemicro.com>
R: Arien Judge <arien.judge@morsemicro.com>
L: linux-wireless@vger.kernel.org
S: Supported
F: drivers/net/wireless/morsemicro/
MOST(R) TECHNOLOGY DRIVER
M: Parthiban Veerasooran <parthiban.veerasooran@microchip.com>
M: Christian Gromm <christian.gromm@microchip.com>
@@ -19573,6 +19590,13 @@ S: Maintained
F: Documentation/devicetree/bindings/ptp/nxp,ptp-netc.yaml
F: drivers/ptp/ptp_netc.c
NXP NXPWIFI WIRELESS DRIVER
M: Jeff Chen <jeff.chen_1@nxp.com>
R: Francesco Dolcini <francesco@dolcini.it>
L: linux-wireless@vger.kernel.org
S: Maintained
F: drivers/net/wireless/nxp/
NXP PF5300/PF5301/PF5302 PMIC REGULATOR DEVICE DRIVER
M: Woodrow Douglass <wdouglass@carnegierobotics.com>
S: Maintained
@@ -27998,7 +28022,7 @@ M: Thangaraj Samynathan <Thangaraj.S@microchip.com>
M: UNGLinuxDriver@microchip.com
L: netdev@vger.kernel.org
S: Maintained
F: Documentation/devicetree/bindings/net/microchip,lan78xx.txt
F: Documentation/devicetree/bindings/net/microchip,lan7800.yaml
F: drivers/net/usb/lan78xx.*
F: include/dt-bindings/net/microchip-lan78xx.h
-1
View File
@@ -210,7 +210,6 @@ CONFIG_BNX2X=m
CONFIG_CHELSIO_T1=m
CONFIG_BE2NET=m
CONFIG_IBMVETH=m
CONFIG_EHEA=m
CONFIG_IBMVNIC=m
CONFIG_E100=y
CONFIG_E1000=y

Some files were not shown because too many files have changed in this diff Show More