Netdev List
 help / color / mirror / Atom feed
From: Hangbin Liu <liuhangbin@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org, "David S . Miller" <davem@davemloft.net>,
	David Ahern <dsahern@kernel.org>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Ido Schimmel <idosch@idosch.org>,
	Nikolay Aleksandrov <razor@blackwall.org>,
	Roopa Prabhu <roopa@nvidia.com>, Florian Westphal <fw@strlen.de>,
	Andrew Lunn <andrew@lunn.ch>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Vladimir Oltean <olteanv@gmail.com>,
	Jiri Pirko <jiri@resnulli.us>,
	Marc Muehlfeld <mmuehlfe@redhat.com>
Subject: Re: [PATCHv3 net-next 01/10] docs: bridge: update doc format to rst
Date: Wed, 29 Nov 2023 15:34:41 +0800	[thread overview]
Message-ID: <ZWbpkTf4qyAgTAGy@Laptop-X1> (raw)
In-Reply-To: <20231128144609.08b4275b@hermes.local>

On Tue, Nov 28, 2023 at 02:46:09PM -0800, Stephen Hemminger wrote:
> On Tue, 28 Nov 2023 16:49:34 +0800
> Hangbin Liu <liuhangbin@gmail.com> wrote:
> 
> > The current bridge kernel doc is too old. It only pointed to the
> > linuxfoundation wiki page which lacks of the new features.
> > 
> > Here let's start the new bridge document and put all the bridge info
> > so new developers and users could catch up the last bridge status soon.
> > 
> > In this patch, Convert the doc to rst format. Add bridge brief introduction,
> > FAQ and contact info.
> > 
> > Signed-off-by: Hangbin Liu <liuhangbin@gmail.com>
> 
> Should also reference and borrow definitions from the IEEE 802.1D standard.

Hi Stephen,

Do you mean to use the definitions from the IEEE 802.1D in the doc?

Something like:

The IEEE 802.1D standard defines the operation of bridges in computer networks.
A bridge, in the context of this standard, is a device that connects two or more
network segments and operates at the data link layer (Layer 2) of the OSI
(Open Systems Interconnection) model. The purpose of a bridge is to filter and
forward frames between different segments based on the destination MAC
(Media Access Control) address.

Thanks
Hangbin

  reply	other threads:[~2023-11-29  7:34 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-28  8:49 [PATCHv3 net-next 00/10] Doc: update bridge doc Hangbin Liu
2023-11-28  8:49 ` [PATCHv3 net-next 01/10] docs: bridge: update doc format to rst Hangbin Liu
2023-11-28 22:46   ` Stephen Hemminger
2023-11-29  7:34     ` Hangbin Liu [this message]
2023-11-29  4:16   ` Florian Fainelli
2023-11-28  8:49 ` [PATCHv3 net-next 02/10] net: bridge: add document for IFLA_BR enum Hangbin Liu
2023-11-29 18:37   ` Vladimir Oltean
2023-11-28  8:49 ` [PATCHv3 net-next 03/10] net: bridge: add document for IFLA_BRPORT enum Hangbin Liu
2023-11-28  8:49 ` [PATCHv3 net-next 04/10] docs: bridge: Add kAPI/uAPI fields Hangbin Liu
2023-11-28 22:47   ` Stephen Hemminger
2023-11-29  4:11   ` Florian Fainelli
2023-11-28  8:49 ` [PATCHv3 net-next 05/10] docs: bridge: add STP doc Hangbin Liu
2023-11-28 22:48   ` Stephen Hemminger
2023-11-29  7:43     ` Hangbin Liu
2023-11-29 15:10       ` Stephen Hemminger
2023-11-29 18:46       ` Vladimir Oltean
2023-11-29  4:21   ` Florian Fainelli
2023-11-29 18:48   ` Vladimir Oltean
2023-11-28  8:49 ` [PATCHv3 net-next 06/10] docs: bridge: add VLAN doc Hangbin Liu
2023-11-29  4:12   ` Florian Fainelli
2023-11-29 18:40   ` Vladimir Oltean
2023-11-28  8:49 ` [PATCHv3 net-next 07/10] docs: bridge: add multicast doc Hangbin Liu
2023-11-29  4:15   ` Florian Fainelli
2023-11-28  8:49 ` [PATCHv3 net-next 08/10] docs: bridge: add switchdev doc Hangbin Liu
2023-11-29  4:16   ` Florian Fainelli
2023-11-28  8:49 ` [PATCHv3 net-next 09/10] docs: bridge: add netfilter doc Hangbin Liu
2023-11-29  4:18   ` Florian Fainelli
2023-11-28  8:49 ` [PATCHv3 net-next 10/10] docs: bridge: add other features Hangbin Liu
2023-11-29  4:09   ` Florian Fainelli

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZWbpkTf4qyAgTAGy@Laptop-X1 \
    --to=liuhangbin@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=f.fainelli@gmail.com \
    --cc=fw@strlen.de \
    --cc=idosch@idosch.org \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=mmuehlfe@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=pabeni@redhat.com \
    --cc=razor@blackwall.org \
    --cc=roopa@nvidia.com \
    --cc=stephen@networkplumber.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox