netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: jasowang@redhat.com
Cc: willemdebruijn.kernel@gmail.com, netdev@vger.kernel.org,
	mkubecek@suse.cz, willemb@google.com
Subject: Re: [PATCH net] net: accept UFO datagrams from tuntap and packet
Date: Mon, 20 Nov 2017 14:51:31 +0900 (KST)	[thread overview]
Message-ID: <20171120.145131.1367135704576085674.davem@davemloft.net> (raw)
In-Reply-To: <4cbf298f-7ee3-bab7-f512-e5eee2fa7b07@redhat.com>

From: Jason Wang <jasowang@redhat.com>
Date: Mon, 20 Nov 2017 11:03:54 +0800

> Looks good to me. The only concern is that whether or not stable can
> accept this patch:

Stable submission will not be a problem, please do not worry about
it :-)

      reply	other threads:[~2017-11-20  5:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-17 22:59 [PATCH net] net: accept UFO datagrams from tuntap and packet Willem de Bruijn
2017-11-18  1:42 ` David Miller
2017-11-19  0:58   ` Willem de Bruijn
2017-11-20  3:03 ` Jason Wang
2017-11-20  5:51   ` David Miller [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=20171120.145131.1367135704576085674.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=jasowang@redhat.com \
    --cc=mkubecek@suse.cz \
    --cc=netdev@vger.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).