All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin LaHaise <bcrl-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org>
To: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
Cc: dev-yBygre7rU0TnMu66kgdUjQ@public.gmane.org,
	netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	eric.dumazet-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Subject: Re: [PATCH net-next] udp: intoduce udp_encap_needed static_key
Date: Fri, 13 Apr 2012 13:45:13 -0400	[thread overview]
Message-ID: <20120413174513.GC6589@kvack.org> (raw)
In-Reply-To: <20120413.134108.1844473866612154303.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>

Hi folks,

On Fri, Apr 13, 2012 at 01:41:08PM -0400, David Miller wrote:
> Ban, please incorporate this scheme when you respin your
> fixed ipv6 encap/l2tp patches.
> 
> Thanks.

Okay, will do.  Thanks for the feedback and heads up.

		-ben
-- 
"Thought is the essence of where you are now."

  parent reply	other threads:[~2012-04-13 17:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-12  7:42 [RFC v3] Add TCP encap_rcv hook Simon Horman
     [not found] ` <20120412074159.GA10866-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>
2012-04-12  8:20   ` Eric Dumazet
2012-04-12  9:05     ` [PATCH net-next] udp: intoduce udp_encap_needed static_key Eric Dumazet
2012-04-12  9:10       ` Eric Dumazet
2012-04-12 14:35       ` Simon Horman
     [not found]         ` <20120412143552.GA8730-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>
2012-04-12 14:40           ` [RFC v4] Add TCP encap_rcv hook Simon Horman
2012-04-13 17:41       ` [PATCH net-next] udp: intoduce udp_encap_needed static_key David Miller
     [not found]         ` <20120413.134108.1844473866612154303.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2012-04-13 17:45           ` Benjamin LaHaise [this message]
2012-04-12 13:10     ` [RFC v3] Add TCP encap_rcv hook Simon Horman

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=20120413174513.GC6589@kvack.org \
    --to=bcrl-bw31mazkks3ytjvyw6ydsg@public.gmane.org \
    --cc=davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org \
    --cc=dev-yBygre7rU0TnMu66kgdUjQ@public.gmane.org \
    --cc=eric.dumazet-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.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.