From: Vladimir Oltean <olteanv@gmail.com>
To: George McCollister <george.mccollister@gmail.com>
Cc: Jakub Kicinski <kuba@kernel.org>, Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Jonathan Corbet <corbet@lwn.net>,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2 1/4] net: hsr: generate supervision frame without HSR/PRP tag
Date: Sun, 7 Feb 2021 03:26:50 +0200 [thread overview]
Message-ID: <20210207012650.ewehcarai3tep5xa@skbuf> (raw)
In-Reply-To: <20210204215926.64377-2-george.mccollister@gmail.com>
On Thu, Feb 04, 2021 at 03:59:23PM -0600, George McCollister wrote:
> @@ -289,23 +286,12 @@ static void send_hsr_supervision_frame(struct hsr_port *master,
> hsr->announce_count++;
> }
>
> - if (!hsr->prot_version)
> - proto = ETH_P_PRP;
> - else
> - proto = ETH_P_HSR;
> -
> - skb = hsr_init_skb(master, proto);
> + skb = hsr_init_skb(master, ETH_P_PRP);
> if (!skb) {
> WARN_ONCE(1, "HSR: Could not send supervision frame\n");
> return;
> }
I wonder why you aren't even more aggressive, just remove the proto
argument from hsr_init_skb and delay setting skb->protocol to
hsr_fill_tag or the whereabouts. This is probably also more correct
since as far as I can see, nobody is updating the skb->proto of
supervision frames from HSR v0 to v1 after your change.
next prev parent reply other threads:[~2021-02-07 1:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-04 21:59 [PATCH net-next v2 0/4] add HSR offloading support for DSA switches George McCollister
2021-02-04 21:59 ` [PATCH net-next v2 1/4] net: hsr: generate supervision frame without HSR/PRP tag George McCollister
2021-02-07 1:26 ` Vladimir Oltean [this message]
2021-02-08 17:31 ` George McCollister
2021-02-04 21:59 ` [PATCH net-next v2 2/4] net: hsr: add offloading support George McCollister
2021-02-04 21:59 ` [PATCH net-next v2 3/4] net: dsa: add support for offloading HSR George McCollister
2021-02-06 23:29 ` Vladimir Oltean
2021-02-08 17:21 ` George McCollister
2021-02-09 17:20 ` Vladimir Oltean
2021-02-09 18:37 ` George McCollister
2021-02-09 18:51 ` Vladimir Oltean
2021-02-09 19:09 ` George McCollister
2021-02-04 21:59 ` [PATCH net-next v2 4/4] net: dsa: xrs700x: add HSR offloading support George McCollister
2021-02-06 23:53 ` Vladimir Oltean
2021-02-08 14:46 ` George McCollister
2021-02-08 20:16 ` [PATCH net-next v2 0/4] add HSR offloading support for DSA switches Tobias Waldekranz
2021-02-08 21:09 ` George McCollister
2021-02-09 14:38 ` Tobias Waldekranz
2021-02-09 17:04 ` George McCollister
2021-02-09 17:14 ` Vladimir Oltean
2021-02-10 21:10 ` Tobias Waldekranz
2021-02-10 21:55 ` Vladimir Oltean
2021-02-12 23:52 ` Tobias Waldekranz
2021-02-13 0:43 ` Vladimir Oltean
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=20210207012650.ewehcarai3tep5xa@skbuf \
--to=olteanv@gmail.com \
--cc=andrew@lunn.ch \
--cc=corbet@lwn.net \
--cc=f.fainelli@gmail.com \
--cc=george.mccollister@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@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