netdev - [PATCH net-next 1/5] Documentation: networking: switchdev: separate bulleted items with new line

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 17 Mar 2021 19:44:54 +0200
From:   Vladimir Oltean <vladimir.oltean@....com>
To:     netdev@...r.kernel.org, "David S . Miller" <davem@...emloft.net>,
        Jakub Kicinski <kuba@...nel.org>
Cc:     Andrew Lunn <andrew@...n.ch>,
        Florian Fainelli <f.fainelli@...il.com>,
        Vivien Didelot <vivien.didelot@...il.com>,
        Jiri Pirko <jiri@...nulli.us>,
        Ido Schimmel <idosch@...sch.org>,
        Stephen Rothwell <sfr@...b.auug.org.au>
Subject: [PATCH net-next 1/5] Documentation: networking: switchdev: separate bulleted items with new line

It looks like "make htmldocs" produces this warning:
Documentation/networking/switchdev.rst:482: WARNING: Unexpected indentation.

Fixes: 0f22ad45f47c ("Documentation: networking: switchdev: clarify device driver behavior")
Reported-by: Stephen Rothwell <sfr@...b.auug.org.au>
Signed-off-by: Vladimir Oltean <vladimir.oltean@....com>
---
 Documentation/networking/switchdev.rst | 1 +
 1 file changed, 1 insertion(+)

diff --git a/Documentation/networking/switchdev.rst b/Documentation/networking/switchdev.rst
index 1b56367d85ad..aa78102c9fab 100644
--- a/Documentation/networking/switchdev.rst
+++ b/Documentation/networking/switchdev.rst
@@ -479,6 +479,7 @@ is not possible.
   be added to a second bridge, which includes other switch ports or software
   interfaces. Some approaches to ensure that the forwarding domain for traffic
   belonging to the VLAN upper interfaces are managed properly:
+
     * If forwarding destinations can be managed per VLAN, the hardware could be
       configured to map all traffic, except the packets tagged with a VID
       belonging to a VLAN upper interface, to an internal VID corresponding to
-- 
2.25.1