From: Ido Schimmel <idosch@idosch.org>
To: Ted Chen <znscnchen@gmail.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, andrew+netdev@lunn.ch, netdev@vger.kernel.org
Subject: Re: [PATCH RFC net-next 3/3] vxlan: vxlan_rcv(): Update comment to inlucde ipv6
Date: Tue, 4 Feb 2025 16:38:23 +0200 [thread overview]
Message-ID: <Z6ImX7hAB44uUrI0@shredder> (raw)
In-Reply-To: <Z6ISkVTHtknDTPGn@t-dallas>
On Tue, Feb 04, 2025 at 09:13:53PM +0800, Ted Chen wrote:
> I'm ok with either way.
> Please let me know if I need to send a separate one or the current one
> is fine.
Yes, need to resend as a standalone patch.
> > Regardless, please submit this patch separately as it's not related to
> > the other patches in the series.
> I came across this comment when I wrote this series as I found vxlan_rcv()
> is called for both IPV4 and IPV6. Besides, I saw vxlan_err_lookup() has a
> similar comment.
OK, so it makes sense to adjust the comment like you did.
next prev parent reply other threads:[~2025-02-04 14:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-01 11:32 [PATCH RFC net-next 0/3] vxlan: Support of Hub Spoke Network to use the same VNI Ted Chen
2025-02-01 11:34 ` [PATCH RFC net-next 1/3] vxlan: vxlan_vs_find_vni(): Find vxlan_dev according to vni and remote_ip Ted Chen
2025-02-02 11:56 ` Ido Schimmel
2025-02-04 13:09 ` Ted Chen
2025-02-04 14:16 ` Ido Schimmel
2025-02-05 12:27 ` Ted Chen
2025-02-01 11:34 ` [PATCH RFC net-next 2/3] vxlan: Do not treat vxlan dev as used when unicast remote_ip mismatches Ted Chen
2025-02-01 11:34 ` [PATCH RFC net-next 3/3] vxlan: vxlan_rcv(): Update comment to inlucde ipv6 Ted Chen
2025-02-02 12:09 ` Ido Schimmel
2025-02-04 13:13 ` Ted Chen
2025-02-04 14:38 ` Ido Schimmel [this message]
2025-02-02 13:40 ` [PATCH RFC net-next 0/3] vxlan: Support of Hub Spoke Network to use the same VNI Ido Schimmel
2025-02-04 13:27 ` Ted Chen
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=Z6ImX7hAB44uUrI0@shredder \
--to=idosch@idosch.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=znscnchen@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 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.