netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ido Schimmel <idosch@idosch.org>
To: Nikolay Aleksandrov <razor@blackwall.org>
Cc: Ted Chen <znscnchen@gmail.com>,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, andrew+netdev@lunn.ch, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] vxlan: vxlan_rcv(): Update comment to inlucde ipv6
Date: Wed, 5 Feb 2025 19:48:55 +0200	[thread overview]
Message-ID: <Z6OkhzUHMPuSD6YM@shredder> (raw)
In-Reply-To: <e5373a02-959b-4609-8a3f-7e25c69d97b8@blackwall.org>

On Wed, Feb 05, 2025 at 02:48:36PM +0200, Nikolay Aleksandrov wrote:
> On 2/5/25 14:40, Ted Chen wrote:
> > On Wed, Feb 05, 2025 at 02:12:50PM +0200, Nikolay Aleksandrov wrote:
> >> On 2/5/25 13:44, Ted Chen wrote:
> >>> Update the comment to indicate that both net/ipv4/udp.c and net/ipv6/udp.c
> >>> invoke vxlan_rcv() to process packets.
> >>>
> >>> The comment aligns with that for vxlan_err_lookup().
> >>>
> >>> Cc: Ido Schimmel <idosch@idosch.org>
> >>> Signed-off-by: Ted Chen <znscnchen@gmail.com>
> >>> ---
> >>>  drivers/net/vxlan/vxlan_core.c | 2 +-
> >>>  1 file changed, 1 insertion(+), 1 deletion(-)
> >>>
> >>> diff --git a/drivers/net/vxlan/vxlan_core.c b/drivers/net/vxlan/vxlan_core.c
> >>> index 5ef40ac816cc..8bdf91d1fdfe 100644
> >>> --- a/drivers/net/vxlan/vxlan_core.c
> >>> +++ b/drivers/net/vxlan/vxlan_core.c
> >>> @@ -1684,7 +1684,7 @@ static bool vxlan_ecn_decapsulate(struct vxlan_sock *vs, void *oiph,
> >>>  	return err <= 1;
> >>>  }
> >>>  
> >>> -/* Callback from net/ipv4/udp.c to receive packets */
> >>> +/* Callback from net/ipv{4,6}/udp.c to receive packets */
> >>>  static int vxlan_rcv(struct sock *sk, struct sk_buff *skb)
> >>>  {
> >>>  	struct vxlan_vni_node *vninode = NULL;
> >>
> >> Your subject has a typo
> >> s/inlucde/include
> > Oops. Sorry for that.
> >  
> >> IMO these comments are unnecessary, encap_rcv callers are trivial to find.
> > I'm fine with either way. No comment is better than a wrong comment.
> > Please let me know if I need to send a new version to correct the subject or
> > remove the comments for both vxlan_rcv() and vxlan_err_lookup().
> > 
> 
> Up to you, I don't have a strong preference. You have to wait 24 hours
> before posting another version anyway, so you have time to decide. :)

Looks like nobody will miss these comments, so I think they can be
safely removed in v2 :)

      reply	other threads:[~2025-02-05 17:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-05 11:44 [PATCH net-next] vxlan: vxlan_rcv(): Update comment to inlucde ipv6 Ted Chen
2025-02-05 12:12 ` Nikolay Aleksandrov
2025-02-05 12:40   ` Ted Chen
2025-02-05 12:48     ` Nikolay Aleksandrov
2025-02-05 17:48       ` Ido Schimmel [this message]

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=Z6OkhzUHMPuSD6YM@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=razor@blackwall.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).