All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Joe Stringer <joestringer@nicira.com>, netdev@vger.kernel.org
Cc: davem@davemloft.net, pshelar@nicira.com
Subject: Re: [PATCHv4 net 1/6] openvswitch: Fix typos in CT headers
Date: Wed, 7 Oct 2015 16:33:15 +0300	[thread overview]
Message-ID: <56151F1B.6080207@cogentembedded.com> (raw)
In-Reply-To: <1444154401-18029-2-git-send-email-joestringer@nicira.com>

On 10/6/2015 8:59 PM, Joe Stringer wrote:

> These comments hadn't caught up to their implementations, fix them.
>
> Fixes: 7f8a436eaa2c "openvswitch: Add conntrack action"

    Sigh. Please see Documentation/SubmittingPatches. It should be:

Fixes: 7f8a436eaa2c ("openvswitch: Add conntrack action")

> Signed-off-by: Joe Stringer <joestringer@nicira.com>
> Acked-by: Pravin B Shelar <pshelar@nicira.com>

MBR, Sergei

  reply	other threads:[~2015-10-07 13:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-06 17:59 [PATCHv4 net 0/6] OVS conntrack fixes for net Joe Stringer
2015-10-06 17:59 ` [PATCHv4 net 1/6] openvswitch: Fix typos in CT headers Joe Stringer
2015-10-07 13:33   ` Sergei Shtylyov [this message]
2015-10-07 16:12     ` Joe Stringer
2015-10-06 17:59 ` [PATCHv4 net 2/6] openvswitch: Fix skb leak in ovs_fragment() Joe Stringer
2015-10-06 17:59 ` [PATCHv4 net 3/6] openvswitch: Ensure flow is valid before executing ct Joe Stringer
2015-10-06 17:59 ` [PATCHv4 net 4/6] openvswitch: Reject ct_state unsupported bits Joe Stringer
2015-10-06 18:00 ` [PATCHv4 net 5/6] openvswitch: Extend ct_state match field to 32 bits Joe Stringer
2015-10-06 18:00 ` [PATCHv4 net 6/6] openvswitch: Change CT_ATTR_FLAGS to CT_ATTR_COMMIT Joe Stringer
2015-10-07 12:03 ` [PATCHv4 net 0/6] OVS conntrack fixes for net 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=56151F1B.6080207@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=davem@davemloft.net \
    --cc=joestringer@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 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.