All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, jesse@nicira.com
Subject: Re: [PATCH v2] geneve: remove use of internal IP header when calling IP_ECN_decapsulate
Date: Mon, 21 Sep 2015 10:04:32 -0400	[thread overview]
Message-ID: <20150921140432.GB18632@tuxdriver.com> (raw)
In-Reply-To: <20150920.222459.2251924175671848436.davem@davemloft.net>

On Sun, Sep 20, 2015 at 10:24:59PM -0700, David Miller wrote:
> From: "John W. Linville" <linville@tuxdriver.com>
> Date: Thu, 17 Sep 2015 16:34:54 -0400
> 
> > This seems to have been a "thinko".  IP_ECN_decapsulate needs info
> > from both internal and external headers.
> > 
> > Signed-off-by: John W. Linville <linville@tuxdriver.com>
> > ---
> > v2 -- ensure the collect_md path still calls IP_ECN_decapsulate
> 
> Judging by the discussion on this patch, I expect that this will
> be respun to make the TX path match what we'll be doing in the RX
> path here.

Yup -- planning to do that this morning!

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

  reply	other threads:[~2015-09-21 14:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-17 17:17 [PATCH] geneve: remove use of internal IP header when calling IP_ECN_decapsulate John W. Linville
2015-09-17 19:46 ` Jesse Gross
2015-09-17 20:17   ` John W. Linville
2015-09-17 20:34 ` [PATCH v2] " John W. Linville
2015-09-18 20:30   ` Jesse Gross
2015-09-18 20:40     ` John W. Linville
2015-09-18 21:49       ` Jesse Gross
2015-09-19  1:36         ` John W. Linville
2015-09-19  2:19           ` Jesse Gross
2015-09-21  5:24   ` David Miller
2015-09-21 14:04     ` John W. Linville [this message]
2015-09-21 14:29     ` [PATCH v3] geneve: ensure ECN info is handled properly in all tx/rx paths John W. Linville
2015-09-22  1:11       ` Jesse Gross
2015-09-22 23:50       ` David Miller

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=20150921140432.GB18632@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=davem@davemloft.net \
    --cc=jesse@nicira.com \
    --cc=netdev@vger.kernel.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.