The 'dsa-tag-protocol' is used to force a switch tree to use a
particular tag protocol, typically because the Ethernet controller
that it is connected to is not compatible with the default one.
Signed-off-by: Tobias Waldekranz
---
Documentation/devicetree/bindings/net/dsa/dsa.yaml | 9 +
On Thu, Apr 15, 2021 at 04:27:58PM -0500, Rob Herring wrote:
> On Thu, Apr 15, 2021 at 11:26:10AM +0200, Tobias Waldekranz wrote:
> > The 'dsa,tag-protocol' is used to force a switch tree to use a
> > particular tag protocol, typically because the Ethernet controller
> > that it is connected to is
Add documentation for ETHTOOL_MSG_STATS_GET.
Signed-off-by: Jakub Kicinski
---
Documentation/networking/ethtool-netlink.rst | 82
1 file changed, 82 insertions(+)
diff --git a/Documentation/networking/ethtool-netlink.rst
b/Documentation/networking/ethtool-netlink.rst
index
using
the phy node.
Document the above implementation in the bosch mcan bindings
Signed-off-by: Faiz Abbas
Signed-off-by: Aswath Govindraju
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/net/can/bosch,m_can.yaml | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation
Add documentation for ETHTOOL_MSG_STATS_GET.
Signed-off-by: Jakub Kicinski
---
Documentation/networking/ethtool-netlink.rst | 82
1 file changed, 82 insertions(+)
diff --git a/Documentation/networking/ethtool-netlink.rst
b/Documentation/networking/ethtool-netlink.rst
index
uration done in the
> phy driver. The bit rate limitation can the be obtained by the driver using
> the phy node.
>
> Document the above implementation in the bosch mcan bindings
>
> Signed-off-by: Faiz Abbas
> Signed-off-by: Aswath Govindraju
> ---
> Documentation/de
On Thu, Apr 15, 2021 at 11:26:10AM +0200, Tobias Waldekranz wrote:
> The 'dsa,tag-protocol' is used to force a switch tree to use a
> particular tag protocol, typically because the Ethernet controller
> that it is connected to is not compatible with the default one.
>
> Signed-off-by: Tobias Walde
using
the phy node.
Document the above implementation in the bosch mcan bindings
Signed-off-by: Faiz Abbas
Signed-off-by: Aswath Govindraju
---
Documentation/devicetree/bindings/net/can/bosch,m_can.yaml | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/devicetree/bindings
using
the phy node.
Document the above implementation in the bosch mcan bindings
Signed-off-by: Faiz Abbas
Signed-off-by: Aswath Govindraju
---
Documentation/devicetree/bindings/net/can/bosch,m_can.yaml | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/devicetree/bindings
The 'dsa,tag-protocol' is used to force a switch tree to use a
particular tag protocol, typically because the Ethernet controller
that it is connected to is not compatible with the default one.
Signed-off-by: Tobias Waldekranz
---
Documentation/devicetree/bindings/net/dsa/dsa.yaml | 9 +
Add documentation for ETHTOOL_MSG_STATS_GET.
Signed-off-by: Jakub Kicinski
---
Documentation/networking/ethtool-netlink.rst | 74
1 file changed, 74 insertions(+)
diff --git a/Documentation/networking/ethtool-netlink.rst
b/Documentation/networking/ethtool-netlink.rst
index
using
the phy node.
Document the above implementation in the bosch mcan bindings
Signed-off-by: Faiz Abbas
Signed-off-by: Aswath Govindraju
---
Documentation/devicetree/bindings/net/can/bosch,m_can.yaml | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/devicetree/bindings
configuration step (for example, pulling the
> >> standby or enable lines) for them to start sending messages. The
> >> transceiver can be implemented as a phy with the configuration done in the
> >> phy driver. The bit rate limitation can the be obtained by the driver using
>
essages. The
>> transceiver can be implemented as a phy with the configuration done in the
>> phy driver. The bit rate limitation can the be obtained by the driver using
>> the phy node.
>>
>> Document the above implementation in the bosch mcan bindings
>>
&g
On 4/9/21 2:00 AM, Yoshihiro Shimoda wrote:
> Document SoC specific bindings for R-Car M3-W+ (r8a77961) SoC.
>
> Also as R8A7796 is now called R8A77960 so that update those
> references.
>
> Signed-off-by: Yoshihiro Shimoda
> Reviewed-by: Geert Uytterhoeven
> Acked-by:
From: Yoshihiro Shimoda
Document SoC specific bindings for R-Car M3-W+ (r8a77961) SoC.
Also as R8A7796 is now called R8A77960 so that update those
references.
Link:
https://lore.kernel.org/r/2021040920.2317696-1-yoshihiro.shimoda...@renesas.com
Signed-off-by: Yoshihiro Shimoda
Reviewed
figuration done in the
> phy driver. The bit rate limitation can the be obtained by the driver using
> the phy node.
>
> Document the above implementation in the bosch mcan bindings
>
> Signed-off-by: Faiz Abbas
> Signed-off-by: Aswath Govindraju
> ---
> Docum
On Fri, 09 Apr 2021 23:43:20 +0530, Radhey Shyam Pandey wrote:
> Convert the bindings document for Xilinx AXI Ethernet Subsystem
> from txt to yaml. No changes to existing binding description.
>
> Signed-off-by: Radhey Shyam Pandey
> ---
> Pending: Fix below remaining dt_bin
Convert the bindings document for Xilinx AXI Ethernet Subsystem
from txt to yaml. No changes to existing binding description.
Signed-off-by: Radhey Shyam Pandey
---
Pending: Fix below remaining dt_binding_check warning:
ethernet@40c0: 'device_type' does not match any of
t
using
the phy node.
Document the above implementation in the bosch mcan bindings
Signed-off-by: Faiz Abbas
Signed-off-by: Aswath Govindraju
---
Documentation/devicetree/bindings/net/can/bosch,m_can.yaml | 6 ++
1 file changed, 6 insertions(+)
diff --git a/Documentation/devicetree/bindings
On Tue, Apr 06, 2021 at 03:30:46PM +0200, Andrew Lunn wrote:
> > Andrew, Vladimir: I will just list dsa and edsa for now. If it is needed
> > on other devices, people can add them to the list after they have tested
> > their drivers. Fair?
>
> O.K.
Same here.
d apply cleanly to both trees.
>
> [...]
Here is the summary with links:
- [net-next] ethtool: document PHY tunable callbacks
https://git.kernel.org/netdev/net-next/c/56f15e2cb1f7
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
On 4/6/2021 5:23 PM, Jakub Kicinski wrote:
> Add missing kdoc for phy tunable callbacks.
>
> Signed-off-by: Jakub Kicinski
Reviewed-by: Florian Fainelli
--
Florian
On Tue, Apr 06, 2021 at 05:23:59PM -0700, Jakub Kicinski wrote:
> Add missing kdoc for phy tunable callbacks.
>
> Signed-off-by: Jakub Kicinski
Reviewed-by: Andrew Lunn
Andrew
Add a note on expected handling of reserved fields,
and references to all kdocs. This fixes a bunch
of kdoc warnings.
Signed-off-by: Jakub Kicinski
---
include/uapi/linux/ethtool.h | 22 +-
1 file changed, 21 insertions(+), 1 deletion(-)
diff --git a/include/uapi/linux/ethto
Add missing kdoc for phy tunable callbacks.
Signed-off-by: Jakub Kicinski
---
Targetting net-next to avoid conflict with upcoming patches.
Should apply cleanly to both trees.
include/linux/ethtool.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/linux/ethtool.h b/include/linux/et
> Andrew, Vladimir: I will just list dsa and edsa for now. If it is needed
> on other devices, people can add them to the list after they have tested
> their drivers. Fair?
O.K.
Andrew
On Sat, Mar 27, 2021 at 12:13, Rob Herring wrote:
> On Fri, Mar 26, 2021 at 11:56:48AM +0100, Tobias Waldekranz wrote:
>> The 'dsa,tag-protocol' is used to force a switch tree to use a
>> particular tag protocol, typically because the Ethernet controller
>> that it is connected to is not compatibl
if (inet_is_local_reserved_port(net, port))
> continue;
>
> [...]
Here is the summary with links:
- [net-next] net: document a side effect of ip_local_reserved_ports
https://git.kernel.org/netdev/net-next/c/a7a80b17c750
You are awesome, t
If there is overlapp between ip_local_port_range and
ip_local_reserved_ports with a huge reserved block, it will affect probability
of selecting ephemeral ports, see file net/ipv4/inet_hashtables.c:723
int __inet_hash_connect(
...
for (i = 0; i < remaining; i += 2, port +
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Mon, 29 Mar 2021 17:57:31 +0200 you wrote:
> Add a document describing the principles behind resilient next-hop groups,
> and some notes about how to configure and offload them.
>
> Suggested-by: David Ahe
On Mon, Mar 29, 2021 at 05:57:31PM +0200, Petr Machata wrote:
> Add a document describing the principles behind resilient next-hop groups,
> and some notes about how to configure and offload them.
>
> Suggested-by: David Ahern
> Signed-off-by: Petr Machata
> Reviewed-by: Davi
Add a document describing the principles behind resilient next-hop groups,
and some notes about how to configure and offload them.
Suggested-by: David Ahern
Signed-off-by: Petr Machata
Reviewed-by: David Ahern
---
Notes:
v1 (from an RFC shared privately):
- Dropped a reference to a
On Fri, Mar 26, 2021 at 11:56:48AM +0100, Tobias Waldekranz wrote:
> The 'dsa,tag-protocol' is used to force a switch tree to use a
> particular tag protocol, typically because the Ethernet controller
> that it is connected to is not compatible with the default one.
>
> Signed-off-by: Tobias Walde
kdoc does not have good support for documenting defines,
and we can't abuse the enum documentation because it
generates warnings.
Signed-off-by: Jakub Kicinski
---
include/uapi/linux/ethtool.h | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/include/uapi
On Thu, Mar 25, 2021 at 06:04:37PM -0600, Robert Hancock wrote:
> Update DT bindings to describe all of the clocks that the axienet
> driver will now be able to make use of.
>
> Acked-by: Rob Herring
> Signed-off-by: Robert Hancock
Reviewed-by: Andrew Lunn
Andrew
The 'dsa,tag-protocol' is used to force a switch tree to use a
particular tag protocol, typically because the Ethernet controller
that it is connected to is not compatible with the default one.
Signed-off-by: Tobias Waldekranz
---
Documentation/devicetree/bindings/net/dsa/dsa.yaml | 7 +++
1
Update DT bindings to describe all of the clocks that the axienet
driver will now be able to make use of.
Acked-by: Rob Herring
Signed-off-by: Robert Hancock
---
.../bindings/net/xilinx_axienet.txt | 25 ++-
1 file changed, 19 insertions(+), 6 deletions(-)
diff --git
On Wed, Mar 24, 2021 at 11:19 AM Robert Hancock
wrote:
>
> On Wed, 2021-03-24 at 11:08 -0600, Rob Herring wrote:
> > On Fri, Mar 12, 2021 at 01:52:13PM -0600, Robert Hancock wrote:
> > > Update DT bindings to describe all of the clocks that the axienet
> > > driver will now be able to make use of.
On Wed, 2021-03-24 at 11:08 -0600, Rob Herring wrote:
> On Fri, Mar 12, 2021 at 01:52:13PM -0600, Robert Hancock wrote:
> > Update DT bindings to describe all of the clocks that the axienet
> > driver will now be able to make use of.
> >
> > Signed-off-by: Robert Hancock
> > ---
> > .../bindings
On Fri, Mar 12, 2021 at 01:52:13PM -0600, Robert Hancock wrote:
> Update DT bindings to describe all of the clocks that the axienet
> driver will now be able to make use of.
>
> Signed-off-by: Robert Hancock
> ---
> .../bindings/net/xilinx_axienet.txt | 25 ++-
> 1 file
From: Vladimir Oltean
The documentation was already lagging behind by not mentioning the old
version of port_bridge_flags (port_set_egress_floods). So now we are
skipping one step and just explaining how a DSA driver should configure
address learning and flooding settings.
Signed-off-by: Vladimi
Update DT bindings to describe all of the clocks that the axienet
driver will now be able to make use of.
Signed-off-by: Robert Hancock
---
.../bindings/net/xilinx_axienet.txt | 25 ++-
1 file changed, 19 insertions(+), 6 deletions(-)
diff --git a/Documentation/devicet
; devicet...@vger.kernel.org; Robert Hancock
> >
> > Subject: [PATCH net-next v2 1/2] dt-bindings: net: xilinx_axienet: Document
> > additional clocks
> >
> > Update DT bindings to describe all of the clocks that the axienet driver
> > wil
v2 1/2] dt-bindings: net: xilinx_axienet: Document
> additional clocks
>
> Update DT bindings to describe all of the clocks that the axienet driver will
> now be able to make use of.
>
> Signed-off-by: Robert Hancock
> ---
> .../bindings/net/xilinx_axienet.txt | 25
Update DT bindings to describe all of the clocks that the axienet
driver will now be able to make use of.
Signed-off-by: Robert Hancock
---
.../bindings/net/xilinx_axienet.txt | 25 ++-
1 file changed, 19 insertions(+), 6 deletions(-)
diff --git a/Documentation/devicet
[PATCH net-next 1/2] dt-bindings: net: xilinx_axienet: Document
> additional clocks
>
> Update DT bindings to describe all of the clocks that the axienet driver will
> now be able to make use of.
>
> Signed-off-by: Robert Hancock
> ---
> .../bindings/net/xilinx_axienet.
Update DT bindings to describe all of the clocks that the axienet
driver will now be able to make use of.
Signed-off-by: Robert Hancock
---
.../bindings/net/xilinx_axienet.txt | 23 ++-
1 file changed, 17 insertions(+), 6 deletions(-)
diff --git a/Documentation/devicet
hanges in v4:
- More cleanup
Changes in v3: None
Changes in v2:
- Updated with more description in document
Documentation/firmware-guide/acpi/dsd/phy.rst | 133 ++
1 file changed, 133 insertions(+)
create mode 100644 Documentation/firmware-guide/acpi/dsd/phy.rst
diff --git a/Do
On Thu, Feb 11, 2021 at 06:50:15PM +0100, AngeloGioacchino Del Regno wrote:
> MSM8998 support has been added: document the new compatible.
>
> Signed-off-by: AngeloGioacchino Del Regno
>
> ---
> Documentation/devicetree/bindings/net/qcom,ipa.yaml | 1 +
> 1 file
On Thu, Feb 11, 2021 at 06:50:14PM +0100, AngeloGioacchino Del Regno wrote:
> The driver supports SC7180, but the binding was not documented.
> Just add it.
>
> Signed-off-by: AngeloGioacchino Del Regno
>
> ---
> Documentation/devicetree/bindings/net/qcom,ipa.yaml | 6 +-
> 1 file changed,
On 2/11/21 11:50 AM, AngeloGioacchino Del Regno wrote:
> The driver supports SC7180, but the binding was not documented.
> Just add it.
I hadn't noticed that!
I'm trying to get through reviewing your series
today and this will take another hour or so to
go validate to my satisfaction.
Would you
On 2/11/21 11:50 AM, AngeloGioacchino Del Regno wrote:
> MSM8998 support has been added: document the new compatible.
>
> Signed-off-by: AngeloGioacchino Del Regno
>
With the previous patch in place, this becomes almost
automatic.
But I don't want to claim support for a plat
> + the bridge port flags for the CPU port. The assumption is that address
> + learning should be statically enabled (if supported by the hardware) on the
> + CPU port, and flooding towards the CPU port should also be enabled, in lack
> + of an explicit address filtering mechanism in the DSA co
On 2/21/2021 13:33, Vladimir Oltean wrote:
From: Vladimir Oltean
The documentation was already lagging behind by not mentioning the old
version of port_bridge_flags (port_set_egress_floods). So now we are
skipping one step and just explaining how a DSA driver should configure
address learnin
From: Vladimir Oltean
The documentation was already lagging behind by not mentioning the old
version of port_bridge_flags (port_set_egress_floods). So now we are
skipping one step and just explaining how a DSA driver should configure
address learning and flooding settings.
Signed-off-by: Vladimi
eanup
Changes in v3: None
Changes in v2:
- Updated with more description in document
Documentation/firmware-guide/acpi/dsd/phy.rst | 133 ++
1 file changed, 133 insertions(+)
create mode 100644 Documentation/firmware-guide/acpi/dsd/phy.rst
diff --git a/Documentation/firmware-gu
From: Joe Stringer
Based roughly on the following commits:
* Commit cb4d03ab499d ("bpf: Add generic support for lookup batch op")
* Commit 057996380a42 ("bpf: Add batch ops to all htab bpf map")
* Commit aa2e93b8e58e ("bpf: Add generic support for update and delete
batch ops")
Reviewed-by: Que
From: Joe Stringer
Commit 468e2f64d220 ("bpf: introduce BPF_PROG_QUERY command") originally
introduced this, but there have been several additions since then.
Unlike BPF_PROG_ATTACH, it appears that the sockmap progs are not able
to be queried so far.
Reviewed-by: Quentin Monnet
Signed-off-by:
From: Joe Stringer
Based on a brief read of the corresponding source code.
Reviewed-by: Quentin Monnet
Signed-off-by: Joe Stringer
---
include/uapi/linux/bpf.h | 14 +++---
1 file changed, 11 insertions(+), 3 deletions(-)
diff --git a/include/uapi/linux/bpf.h b/include/uapi/linux/bpf
From: Joe Stringer
Document the prog attach command in more detail, based on git commits:
* commit f4324551489e ("bpf: add BPF_PROG_ATTACH and BPF_PROG_DETACH
commands")
* commit 4f738adba30a ("bpf: create tcp_bpf_ulp allowing BPF to monitor
socket TX/RX data")
* commit
From: Joe Stringer
Commit b2197755b263 ("bpf: add support for persistent maps/progs")
contains the original implementation and git logs, used as reference for
this documentation.
Also pull in the filename restriction as documented in commit 6d8cb045cde6
("bpf: comment why dots in filenames under
From: Joe Stringer
Document the meaning of the BPF_F_LOCK flag for the map lookup/update
descriptions. Based on commit 96049f3afd50 ("bpf: introduce BPF_F_LOCK
flag").
Reviewed-by: Quentin Monnet
Signed-off-by: Joe Stringer
---
CC: Alexei Starovoitov
---
include/uapi/linux/
The driver supports SC7180, but the binding was not documented.
Just add it.
Signed-off-by: AngeloGioacchino Del Regno
---
Documentation/devicetree/bindings/net/qcom,ipa.yaml | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/net/qcom,ipa.
MSM8998 support has been added: document the new compatible.
Signed-off-by: AngeloGioacchino Del Regno
---
Documentation/devicetree/bindings/net/qcom,ipa.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/net/qcom,ipa.yaml
b/Documentation/devicetree
From: Vladimir Oltean
The bridge does this:
fdb_modify:
/* Assume permanent */
if (!(req.ndm.ndm_state&(NUD_PERMANENT|NUD_REACHABLE)))
req.ndm.ndm_state |= NUD_PERMANENT;
So let's make the user aware of the fact that if they don't want local
entries, they need to
From: Vladimir Oltean
The bridge program parses "local" and "permanent" in just the same way,
so it makes sense to tell that to users:
fdb_modify:
} else if (matches(*argv, "local") == 0 ||
matches(*argv, "permanent") == 0) {
req
From: Rafał Miłecki
BCM4908 is a family of SoCs with integrated Ethernet controller.
Signed-off-by: Rafał Miłecki
---
V3: Use ethernet-controller.yaml#
Rename "compatible" value (use "-")
Drop "interrupt-names" until it's needed
---
.../bindings/net/brcm,bcm4908-enet.yaml | 43 ++
On 09.02.2021 22:43, Rob Herring wrote:
On Sun, Feb 07, 2021 at 11:26:31PM +0100, Rafał Miłecki wrote:
From: Rafał Miłecki
BCM4908 is a family of SoCs with integrated Ethernet controller.
Signed-off-by: Rafał Miłecki
---
.../bindings/net/brcm,bcm4908enet.yaml| 45 ++
From: Rafał Miłecki
BCM4908 is a family of SoCs with integrated Ethernet controller.
Signed-off-by: Rafał Miłecki
---
V3: Use ethernet-controller.yaml#
Rename "compatible" value (use "-")
Drop "interrupt-names" until it's needed
---
.../bindings/net/brcm,bcm4908-enet.yaml | 43 ++
On Sun, Feb 07, 2021 at 11:26:31PM +0100, Rafał Miłecki wrote:
> From: Rafał Miłecki
>
> BCM4908 is a family of SoCs with integrated Ethernet controller.
>
> Signed-off-by: Rafał Miłecki
> ---
> .../bindings/net/brcm,bcm4908enet.yaml| 45 +++
> 1 file changed, 45 insert
d-off-by: Jay Vosburgh
>
> ---
> Documentation/networking/ip-sysctl.rst | 19 +++
> 1 file changed, 19 insertions(+)
Here is the summary with links:
- [net] Documentation: networking: ip-sysctl: Document src_valid_mark sysctl
https://git.kernel.org/netdev/net-next/c/8cf5d8
robed and registered using
> > +fwnode_mdiobus_register_phy().
> > +
> > +Later, for connecting these PHYs to MAC, the PHYs registered on the
>
> to a MAC,
Each PHY is connected to a MAC. So I'll change it to "PHYs to t
Provide documentation for src_valid_mark sysctl, which was added
in commit 28f6aeea3f12 ("net: restore ip source validation").
Signed-off-by: Jay Vosburgh
---
Documentation/networking/ip-sysctl.rst | 19 +++
1 file changed, 19 insertions(+)
diff --git a/Documentation/ne
HYs in ACPI
> +=
> +
> +The PHYs on an MDIO bus [1] are probed and registered using
> +fwnode_mdiobus_register_phy().
> +
> +Later, for connecting these PHYs to MAC, the PHYs registered on the
to a MAC,
> +MDI
ges in v2:
- Updated with more description in document
Documentation/firmware-guide/acpi/dsd/phy.rst | 133 ++
1 file changed, 133 insertions(+)
create mode 100644 Documentation/firmware-guide/acpi/dsd/phy.rst
diff --git a/Documentation/firmware-guide/acpi/dsd/phy.rst
b/Document
From: Rafał Miłecki
BCM4908 is a family of SoCs with integrated Ethernet controller.
Signed-off-by: Rafał Miłecki
---
.../bindings/net/brcm,bcm4908enet.yaml| 45 +++
1 file changed, 45 insertions(+)
create mode 100644 Documentation/devicetree/bindings/net/brcm,bcm4908e
From: Rafał Miłecki
BCM4908 is a family of SoCs with integrated Ethernet controller.
Signed-off-by: Rafał Miłecki
---
.../bindings/net/brcm,bcm4908enet.yaml| 45 +++
1 file changed, 45 insertions(+)
create mode 100644 Documentation/devicetree/bindings/net/brcm,bcm4908e
On Fri, Jan 29, 2021 at 6:44 PM Rafael J. Wysocki wrote:
> On Fri, Jan 29, 2021 at 5:37 PM Rafael J. Wysocki wrote:
> > On Fri, Jan 29, 2021 at 7:48 AM Calvin Johnson
> > wrote:
...
> > It would work, but I would introduce a wrapper around the _ADR
> > evaluation, something like:
> >
> > int a
be connected to MAC.
> > > > > > > >
> > > > > > > > Describe properties "phy-handle" and "phy-mode".
> > > > > > > >
> > > > > > > > Signed-of
> > > > > Signed-off-by: Calvin Johnson
> > > > > > > ---
> > > > > > >
> > > > > > > Changes in v4:
> > > > > > > - More cleanup
> > > > > >
> > >
t; > > > > Describe properties "phy-handle" and "phy-mode".
> > > > > >
> > > > > > Signed-off-by: Calvin Johnson
> > > > > > ---
> > > > > >
> > > > > > Cha
From: Vladimir Oltean
The existence of dsa_broadcast has generated some confusion in the past:
https://www.mail-archive.com/netdev@vger.kernel.org/msg365042.html
So let's document the existing dsa_port_notify and dsa_broadcast
functions and explain when each of them should be used.
Als
ed-off-by: Calvin Johnson
> > > > > ---
> > > > >
> > > > > Changes in v4:
> > > > > - More cleanup
> > > >
> > > > This looks much better that the previous versions IMV, some nits below.
> > > >
> >
> >
> > > > Describe properties "phy-handle" and "phy-mode".
> > > >
> > > > Signed-off-by: Calvin Johnson
> > > > ---
> > > >
> > > > Changes in v4:
> > > > - More cleanup
> > >
> > &
in Johnson
> > > ---
> > >
> > > Changes in v4:
> > > - More cleanup
> >
> > This looks much better that the previous versions IMV, some nits below.
> >
> > > Changes in v3: None
> > > Changes in v2:
> > > - Updated
revious versions IMV, some nits below.
>
> > Changes in v3: None
> > Changes in v2:
> > - Updated with more description in document
> >
> > Documentation/firmware-guide/acpi/dsd/phy.rst | 129 ++
> > 1 file changed, 129 insertions(+)
&
Document qmap/mux_id sysfs file showing qmimux interface id
Signed-off-by: Daniele Palmas
---
Documentation/ABI/testing/sysfs-class-net-qmi | 10 ++
1 file changed, 10 insertions(+)
diff --git a/Documentation/ABI/testing/sysfs-class-net-qmi
b/Documentation/ABI/testing/sysfs-class-net
Document qmap/mux_id sysfs file showing qmimux interface id
Signed-off-by: Daniele Palmas
---
Documentation/ABI/testing/sysfs-class-net-qmi | 10 ++
1 file changed, 10 insertions(+)
diff --git a/Documentation/ABI/testing/sysfs-class-net-qmi
b/Documentation/ABI/testing/sysfs-class-net
From: Vladimir Oltean
The existence of dsa_broadcast has generated some confusion in the past:
https://www.mail-archive.com/netdev@vger.kernel.org/msg365042.html
So let's document the existing dsa_port_notify and dsa_broadcast
functions and explain when each of them should be used.
Als
Daniele Palmas writes:
> Document qmap/mux_id sysfs file showing qmimux interface id
>
> Signed-off-by: Daniele Palmas
Acked-by: Bjørn Mork
: Pali Rohár
> ---
> Documentation/networking/ip-sysctl.rst | 12
> 1 file changed, 12 insertions(+)
Here is the summary with links:
- doc: networking: ip-sysctl: Document conf/all/disable_ipv6 and
conf/default/disable_ipv6
https://git.kernel.org/netdev/net/c/fc024c5c07aa
You a
> ---
>
> Changes in v4:
> - More cleanup
This looks much better that the previous versions IMV, some nits below.
> Changes in v3: None
> Changes in v2:
> - Updated with more description in document
>
> Documentation/firmware-guide/acpi/dsd/phy.rst | 129 +
more description in document
Documentation/firmware-guide/acpi/dsd/phy.rst | 129 ++
1 file changed, 129 insertions(+)
create mode 100644 Documentation/firmware-guide/acpi/dsd/phy.rst
diff --git a/Documentation/firmware-guide/acpi/dsd/phy.rst
b/Documentation/firmware-guide/acpi/dsd/p
From: Vladimir Oltean
Since this feature's introduction in commit 9c66d1564676 ("taprio: Add
support for hardware offloading") from kernel v5.4, it never got
documented in the man pages. Due to this reason, we see customer reports
of seemingly contradictory information: the community manpages cla
On 1/21/21 5:37 PM, Vladimir Oltean wrote:
> On Thu, Jan 21, 2021 at 04:10:06PM -0700, David Ahern wrote:
>> On 1/21/21 2:57 PM, Vladimir Oltean wrote:
>>> On Thu, Jan 21, 2021 at 11:47:08PM +0200, Vladimir Oltean wrote:
+Enables the full-offload feature. In this mode, taprio will pass the gat
On Thu, Jan 21, 2021 at 04:10:06PM -0700, David Ahern wrote:
> On 1/21/21 2:57 PM, Vladimir Oltean wrote:
> > On Thu, Jan 21, 2021 at 11:47:08PM +0200, Vladimir Oltean wrote:
> >> +Enables the full-offload feature. In this mode, taprio will pass the gate
> >> +control list to the NIC which will exe
On 1/21/21 2:57 PM, Vladimir Oltean wrote:
> On Thu, Jan 21, 2021 at 11:47:08PM +0200, Vladimir Oltean wrote:
>> +Enables the full-offload feature. In this mode, taprio will pass the gate
>> +control list to the NIC which will execute cyclically it in hardware.
>
> Ugh, I meant "execute it cyclica
On Thu, Jan 21, 2021 at 11:47:08PM +0200, Vladimir Oltean wrote:
> +Enables the full-offload feature. In this mode, taprio will pass the gate
> +control list to the NIC which will execute cyclically it in hardware.
Ugh, I meant "execute it cyclically" not "execute cyclically it".
David, could you
From: Vladimir Oltean
Since this feature's introduction in commit 9c66d1564676 ("taprio: Add
support for hardware offloading") from kernel v5.4, it never got
documented in the man pages. Due to this reason, we see customer reports
of seemingly contradictory information: the community manpages cla
1 - 100 of 1230 matches
Mail list logo
