netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: willemdebruijn.kernel@gmail.com
Cc: sashal@kernel.org, nicolas.dichtel@6wind.com,
	netdev@vger.kernel.org, willemb@google.com, maximmi@mellanox.com
Subject: Re: [PATCH net v2] af_packet: fix raw sockets over 6in4 tunnel
Date: Wed, 20 Feb 2019 11:33:01 -0800 (PST)	[thread overview]
Message-ID: <20190220.113301.103790747080622826.davem@davemloft.net> (raw)
In-Reply-To: <CAF=yD-+M=FG+a1ykO5ucBSfE0vvV3C_cNBUH1p55Cy1e7mHA-g@mail.gmail.com>

From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Date: Wed, 20 Feb 2019 13:39:23 -0500

> On Mon, Feb 18, 2019 at 1:50 PM Sasha Levin <sashal@kernel.org> wrote:
>> Should this go to -stable as well? The patch it fixes is in 4.20.
> 
> I believe so. It was also backported to 4.19 stable.

Ok, I'll submit it, thanks.

  reply	other threads:[~2019-02-20 19:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-11 14:43 [PATCH net] af_packet: fix raw sockets over 6in4 tunnel Nicolas Dichtel
2019-01-11 21:29 ` Willem de Bruijn
2019-01-12 18:00   ` Willem de Bruijn
2019-01-14 14:51     ` Nicolas Dichtel
2019-01-14 15:15       ` Willem de Bruijn
2019-01-14 15:38         ` Willem de Bruijn
2019-01-15  9:49           ` Nicolas Dichtel
2019-01-15 16:20             ` Willem de Bruijn
2019-01-17 10:27               ` [PATCH net v2] " Nicolas Dichtel
2019-01-17 15:09                 ` Willem de Bruijn
2019-01-17 23:55                 ` David Miller
2019-02-18 15:57                   ` Sasha Levin
2019-02-20 18:39                     ` Willem de Bruijn
2019-02-20 19:33                       ` David Miller [this message]
2019-02-22 19:50                       ` David Miller
2019-02-22 23:53                         ` Willem de Bruijn
2019-02-25  8:55                           ` Nicolas Dichtel

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=20190220.113301.103790747080622826.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=maximmi@mellanox.com \
    --cc=netdev@vger.kernel.org \
    --cc=nicolas.dichtel@6wind.com \
    --cc=sashal@kernel.org \
    --cc=willemb@google.com \
    --cc=willemdebruijn.kernel@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).