From: Luka Gejak <luka.gejak@linux.dev>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, fmaurer@redhat.com, luka.gejak@linux.dev
Subject: Re: [PATCH net-next v6 0/2] net: hsr: strict supervision TLV validation
Date: Wed, 13 May 2026 20:35:56 +0200 [thread overview]
Message-ID: <7D68E562-7941-46EF-B4B0-AE0DBAD15FC0@linux.dev> (raw)
In-Reply-To: <20260513182657.20346-1-luka.gejak@linux.dev>
On May 13, 2026 8:26:55 PM GMT+02:00, luka.gejak@linux.dev wrote:
>From: Luka Gejak <luka.gejak@linux.dev>
>
...
>Luka Gejak (2):
> net: hsr: require valid EOT supervision TLV
> net: hsr: reject unresolved interlink ifindex
>
> net/hsr/hsr_forward.c | 6 +++---
> net/hsr/hsr_netlink.c | 7 ++++++-
> 2 files changed, 9 insertions(+), 4 deletions(-)
>
Just one note: This series has been resubmitted because it was never
merged due to window being closed and I was instructed by Felix to
resubmit it now. Link to old thread is [1].
Best regards,
Luka Gejak
[1]: https://lore.kernel.org/netdev/20260413103449.169913-1-luka.gejak@linux.dev/
next prev parent reply other threads:[~2026-05-13 18:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 18:26 [PATCH net-next v6 0/2] net: hsr: strict supervision TLV validation luka.gejak
2026-05-13 18:26 ` [PATCH net-next v6 1/2] net: hsr: require valid EOT supervision TLV luka.gejak
2026-05-14 12:55 ` Fernando Fernandez Mancera
2026-05-16 0:33 ` Jakub Kicinski
2026-05-13 18:26 ` [PATCH net-next v6 2/2] net: hsr: reject unresolved interlink ifindex luka.gejak
2026-05-14 12:55 ` Fernando Fernandez Mancera
2026-05-13 18:35 ` Luka Gejak [this message]
2026-05-16 0:40 ` [PATCH net-next v6 0/2] net: hsr: strict supervision TLV validation patchwork-bot+netdevbpf
-- strict thread matches above, loose matches on Subject: below --
2026-04-13 10:34 luka.gejak
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=7D68E562-7941-46EF-B4B0-AE0DBAD15FC0@linux.dev \
--to=luka.gejak@linux.dev \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fmaurer@redhat.com \
--cc=kuba@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.