From: Andrew Lunn <andrew@lunn.ch>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: David Miller <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
David Ahern <dsahern@kernel.org>,
James Prestwood <prestwoj@gmail.com>,
Justin Iurman <justin.iurman@uliege.be>,
Praveen Chaudhary <praveen5582@gmail.com>,
"Jason A . Donenfeld" <Jason@zx2c4.com>,
Eric Dumazet <edumazet@google.com>,
netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next v4 1/3] seg6: export get_srh() for ICMP handling
Date: Wed, 8 Dec 2021 23:37:25 +0100 [thread overview]
Message-ID: <YbEzpTFGl06FXGAS@lunn.ch> (raw)
In-Reply-To: <CA+FuTScGS_s=PCYnXzJbkABOQ7nirg4aa-HwzHjk4crp9vic1w@mail.gmail.com>
On Wed, Dec 08, 2021 at 04:24:56PM -0500, Willem de Bruijn wrote:
> On Wed, Dec 8, 2021 at 12:38 PM Andrew Lunn <andrew@lunn.ch> wrote:
> >
> > From 387a5e9d6b2749d0457ccc760a5b785c2df8f799 Mon Sep 17 00:00:00 2001
> > From: Andrew Lunn <andrew@lunn.ch>
> > Date: Sat, 20 Nov 2021 12:51:07 -0600
> > Subject: [PATCH net-next v4 2/3] icmp: ICMPV6: Examine invoking packet for
> > Segment Route Headers.
>
> Something went wrong when sending this patch series.
>
> The above header is part of the commit message, and this patch is
> marked as 1/3. See also in
> https://patchwork.kernel.org/project/netdevbpf
Now that is odd. I just did the usual git format-patch ; git
send-email.
I will try out v5 sending it just to myself first.
Thanks
Andrew
next prev parent reply other threads:[~2021-12-08 22:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-08 17:38 [PATCH net-next v4 0/3] Fix traceroute in the presence of SRv6 Andrew Lunn
2021-12-08 17:38 ` [PATCH net-next v4 1/3] seg6: export get_srh() for ICMP handling Andrew Lunn
2021-12-08 17:38 ` Andrew Lunn
2021-12-08 21:24 ` Willem de Bruijn
2021-12-08 22:37 ` Andrew Lunn [this message]
2021-12-08 17:38 ` [PATCH net-next v4 3/3] udp6: Use Segment Routing Header for dest address if present Andrew Lunn
2021-12-08 21:26 ` Willem de Bruijn
2021-12-08 22:34 ` Andrew Lunn
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=YbEzpTFGl06FXGAS@lunn.ch \
--to=andrew@lunn.ch \
--cc=Jason@zx2c4.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=justin.iurman@uliege.be \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=praveen5582@gmail.com \
--cc=prestwoj@gmail.com \
--cc=willemdebruijn.kernel@gmail.com \
--cc=yoshfuji@linux-ipv6.org \
/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.