netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: sakiwit@gmail.com
Cc: netdev@vger.kernel.org, pshelar@nicira.com, dev@openvswitch.org
Subject: Re: [PATCH net-next 0/3] Trivial fix-ups for openvswitch
Date: Sun, 10 Jan 2016 23:50:59 -0500 (EST)	[thread overview]
Message-ID: <20160110.235059.452450561151479024.davem@davemloft.net> (raw)
In-Reply-To: <1452380831-11258-1-git-send-email-sakiwit@gmail.com>

From: Jεan Sacren <sakiwit@gmail.com>
Date: Sat,  9 Jan 2016 16:07:08 -0700

> This series does trivial fix-ups for openvswitch as follows:
> 
> 1) Clean up the leftover of the unused function.
> 
> 2) Fix up the twisted struct geneve_port member name.
> 
> 3) Update the kernel doc to reflect the changes in struct vport.

Series applied, thanks.

      reply	other threads:[~2016-01-11  4:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-09 23:07 [PATCH net-next 0/3] Trivial fix-ups for openvswitch Jεan Sacren
2016-01-11  4:50 ` 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=20160110.235059.452450561151479024.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=dev@openvswitch.org \
    --cc=netdev@vger.kernel.org \
    --cc=pshelar@nicira.com \
    --cc=sakiwit@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).