Linux Documentation
 help / color / mirror / Atom feed
From: Christian Melendez <chrismelnu@gmail.com>
To: Jonas Gorski <jonas.gorski@gmail.com>
Cc: "Álvaro Fernández Rojas" <noltari@gmail.com>,
	"Florian Fainelli" <florian.fainelli@broadcom.com>,
	netdev@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: b53.rst: is the 5325/5365 "no tagging support" section still accurate?
Date: Tue, 22 Sep 2026 19:48:01 +0200	[thread overview]
Message-ID: <20260922174801.261426-1-chrismelnu@gmail.com> (raw)
In-Reply-To: <CAOiHx=mJZKk9dT93am0o58Th+yPo2aGj6T4aFWkyeQphPwu4YA@mail.gmail.com>

Hi Jonas,

Thanks for confirming!

Quick follow-up on the "configuration examples look horribly outdated"
part. Once 5325/5365 move to the tagging-supported section, the single
port/bridge/gateway examples further down only apply to 539x/531x5. Were
those outdated specifically for 5325/5365, or wrong in general?

Best regards,
Christian

  reply	other threads:[~2026-09-22 17:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-11 10:35 b53.rst: is the 5325/5365 "no tagging support" section still accurate? Christian Melendez
2026-09-14 14:16 ` Jonas Gorski
2026-09-22 17:48   ` Christian Melendez [this message]
2026-09-22 18:25     ` Jonas Gorski
2026-09-22 21:14       ` [PATCH 1/2] Documentation: dsa: b53: fix stale tagging-support section Christian Melendez
2026-09-22 21:14         ` [PATCH 2/2] MAINTAINERS: add missing entry for b53.rst Christian Melendez
2026-09-23 21:17         ` [PATCH 1/2] Documentation: dsa: b53: fix stale tagging-support section netdev-bot+sashiko
2026-09-26  0:55           ` Jakub Kicinski
2026-09-29  0:00         ` 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=20260922174801.261426-1-chrismelnu@gmail.com \
    --to=chrismelnu@gmail.com \
    --cc=florian.fainelli@broadcom.com \
    --cc=jonas.gorski@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=noltari@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox