From: Pavan Chebbi <pavan.chebbi@broadcom.com>
To: Ivan Vecera <ivecera@redhat.com>
Cc: linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Jonathan Corbet <corbet@lwn.net>,
"open list:NETWORKING [GENERAL]" <netdev@vger.kernel.org>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>
Subject: Re: [PATCH net-next] docs: networking: Fix bridge documentation URL
Date: Tue, 24 Jan 2023 22:10:51 +0530 [thread overview]
Message-ID: <CALs4sv2JF+xksLCFmBefWp7hu2+Mq_pcSO-dDjQrO+9cvD4upQ@mail.gmail.com> (raw)
In-Reply-To: <20230124145127.189221-1-ivecera@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1171 bytes --]
On Tue, Jan 24, 2023 at 8:22 PM Ivan Vecera <ivecera@redhat.com> wrote:
>
> Current documentation URL [1] is no longer valid.
>
> [1] https://www.linuxfoundation.org/collaborate/workgroups/networking/bridge
>
> Signed-off-by: Ivan Vecera <ivecera@redhat.com>
> ---
> Documentation/networking/bridge.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/networking/bridge.rst b/Documentation/networking/bridge.rst
> index 4aef9cddde2f..c859f3c1636e 100644
> --- a/Documentation/networking/bridge.rst
> +++ b/Documentation/networking/bridge.rst
> @@ -8,7 +8,7 @@ In order to use the Ethernet bridging functionality, you'll need the
> userspace tools.
>
> Documentation for Linux bridging is on:
> - http://www.linuxfoundation.org/collaborate/workgroups/networking/bridge
> + https://wiki.linuxfoundation.org/networking/bridge
Maybe there is a reason I don't know why this patch is for net-next and not net.
Change looks good to me.
Reviewed-by: Pavan Chebbi <pavan.chebbi@broadcom.com>
>
> The bridge-utilities are maintained at:
> git://git.kernel.org/pub/scm/linux/kernel/git/shemminger/bridge-utils.git
> --
> 2.38.2
>
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4209 bytes --]
next prev parent reply other threads:[~2023-01-24 16:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 14:51 [PATCH net-next] docs: networking: Fix bridge documentation URL Ivan Vecera
2023-01-24 16:40 ` Pavan Chebbi [this message]
2023-01-26 7:30 ` patchwork-bot+netdevbpf
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=CALs4sv2JF+xksLCFmBefWp7hu2+Mq_pcSO-dDjQrO+9cvD4upQ@mail.gmail.com \
--to=pavan.chebbi@broadcom.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=ivecera@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.