All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pravin Shelar <pshelar@nicira.com>
To: Joe Stringer <joestringer@nicira.com>
Cc: netdev <netdev@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"dev@openvswitch.org" <dev@openvswitch.org>
Subject: Re: [PATCH net-next v14 3/5] openvswitch: Use sw_flow_key_range for key ranges.
Date: Wed, 21 Jan 2015 17:16:24 -0800	[thread overview]
Message-ID: <CALnjE+oXP32Ha+kCxKo-wmQxJ556koD6rhw0LkaeK5tr_4+ZxA@mail.gmail.com> (raw)
In-Reply-To: <1421887372-56414-4-git-send-email-joestringer@nicira.com>

On Wed, Jan 21, 2015 at 4:42 PM, Joe Stringer <joestringer@nicira.com> wrote:
> These minor tidyups make a future patch a little tidier.
>
> Signed-off-by: Joe Stringer <joestringer@nicira.com>

Acked-by: Pravin B Shelar <pshelar@nicira.com>

  reply	other threads:[~2015-01-22  1:16 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-22  0:42 [PATCH net-next v14 0/5] openvswitch: Introduce 128-bit unique flow identifiers Joe Stringer
2015-01-22  0:42 ` Joe Stringer
2015-01-22  0:42 ` [PATCH net-next v14 1/5] openvswitch: Refactor ovs_nla_fill_match() Joe Stringer
2015-01-22  0:42   ` Joe Stringer
2015-01-22  1:16   ` Pravin Shelar
2015-01-22  0:42 ` [PATCH net-next v14 2/5] openvswitch: Refactor ovs_flow_tbl_insert() Joe Stringer
2015-01-22  0:42   ` Joe Stringer
2015-01-22  1:16   ` Pravin Shelar
2015-01-22  1:16     ` Pravin Shelar
2015-01-22  0:42 ` [PATCH net-next v14 3/5] openvswitch: Use sw_flow_key_range for key ranges Joe Stringer
2015-01-22  1:16   ` Pravin Shelar [this message]
2015-01-22  0:42 ` [PATCH net-next v14 4/5] genetlink: Add genlmsg_parse() helper function Joe Stringer
2015-01-22  1:16   ` Pravin Shelar
2015-01-22  0:42 ` [PATCH net-next v14 5/5] openvswitch: Add support for unique flow IDs Joe Stringer
2015-01-22  1:16   ` Pravin Shelar
2015-01-26 23:46 ` [PATCH net-next v14 0/5] openvswitch: Introduce 128-bit unique flow identifiers David Miller
2015-01-26 23:46   ` 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=CALnjE+oXP32Ha+kCxKo-wmQxJ556koD6rhw0LkaeK5tr_4+ZxA@mail.gmail.com \
    --to=pshelar@nicira.com \
    --cc=dev@openvswitch.org \
    --cc=joestringer@nicira.com \
    --cc=linux-kernel@vger.kernel.org \
    --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.