From: Pravin Shelar <pshelar@ovn.org>
To: David Miller <davem@davemloft.net>
Cc: Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next v2 0/4] geneve: Use LWT more effectively.
Date: Mon, 21 Nov 2016 11:03:48 -0800 [thread overview]
Message-ID: <CAOrHB_AL7V3NgqndLkho_YuNOoaawA252HjWzN4tMify+q9SVw@mail.gmail.com> (raw)
In-Reply-To: <20161121.112853.596026767987561055.davem@davemloft.net>
On Mon, Nov 21, 2016 at 8:28 AM, David Miller <davem@davemloft.net> wrote:
> From: Pravin B Shelar <pshelar@ovn.org>
> Date: Fri, 18 Nov 2016 18:10:07 -0800
>
>> Following patch series make use of geneve LWT code path for
>> geneve netdev type of device.
>> This allows us to simplify geneve module.
>>
>> v1-v2:
>> Fix warning reported by kbuild test robot.
>
> This doesn't apply cleanly to net-next, please respin.
>
Sure. I have posted updated series.
Thanks.
prev parent reply other threads:[~2016-11-21 19:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-19 2:10 [PATCH net-next v2 0/4] geneve: Use LWT more effectively Pravin B Shelar
2016-11-19 2:10 ` [PATCH net-next v2 1/4] geneve: Unify LWT and netdev handling Pravin B Shelar
2016-11-19 2:10 ` [PATCH net-next v2 2/4] geneve: Merge ipv4 and ipv6 geneve_build_skb() Pravin B Shelar
2016-11-19 2:10 ` [PATCH net-next v2 3/4] geneve: Remove redundant socket checks Pravin B Shelar
2016-11-19 2:10 ` [PATCH net-next v2 4/4] geneve: Optimize geneve device lookup Pravin B Shelar
2016-11-21 16:28 ` [PATCH net-next v2 0/4] geneve: Use LWT more effectively David Miller
2016-11-21 19:03 ` Pravin Shelar [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=CAOrHB_AL7V3NgqndLkho_YuNOoaawA252HjWzN4tMify+q9SVw@mail.gmail.com \
--to=pshelar@ovn.org \
--cc=davem@davemloft.net \
--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 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).