netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: jesse@nicira.com
Cc: pshelar@nicira.com, netdev@vger.kernel.org, dev@openvswitch.org
Subject: Re: [PATCH net-next v2 0/4] openvswitch tunneling preparation
Date: Fri, 14 Jun 2013 14:04:22 -0700 (PDT)	[thread overview]
Message-ID: <20130614.140422.262779440905577037.davem@davemloft.net> (raw)
In-Reply-To: <CAEP_g=9fV07wM-LVyfyMy9mjKe+y3pkGz8WvbZAPtM096m7ftw@mail.gmail.com>

From: Jesse Gross <jesse@nicira.com>
Date: Fri, 14 Jun 2013 08:28:41 -0700

> On Thu, Jun 13, 2013 at 5:05 PM, David Miller <davem@davemloft.net> wrote:
>> From: Pravin B Shelar <pshelar@nicira.com>
>> Date: Thu, 13 Jun 2013 11:11:19 -0700
>>
>>> Following patches are required but not directly related to ovs tunneling.
>>> So I am sending them as separate series. These cleanups are already
>>> there in out of tree ovs module.
>>>
>>> Since ovs tunneling series depends on this, I am sending all patches
>>> again.
>>
>> Openvswitch folks please send me a pull request.
> 
> For the non-OVS portions of the tunneling series (not this one, which
> I already applied, but the next) do you want to take them directly or
> should I just throw them all into my tree?

I was hoping you would send me a pull request for the initial 4 patch
series et al.  Then get your ACK's for the openvswitch parts of the big
tunneling patch set so that I could just apply the entire thing myself.

  reply	other threads:[~2013-06-14 21:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-13 18:11 [PATCH net-next v2 0/4] openvswitch tunneling preparation Pravin B Shelar
2013-06-14  0:05 ` David Miller
2013-06-14 15:28   ` Jesse Gross
2013-06-14 21:04     ` David Miller [this message]
2013-06-14 22:28       ` Jesse Gross

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=20130614.140422.262779440905577037.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=dev@openvswitch.org \
    --cc=jesse@nicira.com \
    --cc=netdev@vger.kernel.org \
    --cc=pshelar@nicira.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).