netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <simon.horman@netronome.com>
To: John Fastabend <john.r.fastabend@intel.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH flow-net-next] net: flow: Correct spelling of action
Date: Mon, 8 Dec 2014 12:47:18 +0900	[thread overview]
Message-ID: <20141208034715.GA606@vergenet.net> (raw)
In-Reply-To: <54850093.7050900@intel.com>

On Sun, Dec 07, 2014 at 05:36:19PM -0800, John Fastabend wrote:
> On 12/07/2014 05:14 PM, Simon Horman wrote:
> > Signed-off-by: Simon Horman <simon.horman@netronome.com>
> > ---
> >  include/uapi/linux/if_flow.h | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/include/uapi/linux/if_flow.h b/include/uapi/linux/if_flow.h
> > index 25aa744..9255990 100644
> > --- a/include/uapi/linux/if_flow.h
> > +++ b/include/uapi/linux/if_flow.h
> > @@ -356,7 +356,7 @@ enum {
> >   * @uid unique identifier for flow
> >   * @priority priority to execute flow match/action in table
> >   * @match null terminated set of match uids match criteria
> > - * @actoin null terminated set of action uids to apply to match
> > + * @action null terminated set of action uids to apply to match
> >   *
> >   * Flows must match all entries in match set.
> >   */
> > 
> 
> Great thanks Simon! Also I've added a bit so we can
> distinguish between INGRESS pipelines and EGRESS pipelines
> and a bunch of fixes to the netlink processing to check the
> lengths correctly. I'll push those to my tree in the next day or
> so. I'm also porting this to rocker switch now which I hope
> should be ready in the next week for submitting.
> 
> Just to be clear this is against my git tree @
> 
> 	https://github.com/jrfastab/flow-net-next/

Yes, that is right.

Feel free to squash it into existing patches if you prefer.

      reply	other threads:[~2014-12-08  3:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-08  1:14 [PATCH flow-net-next] net: flow: Correct spelling of action Simon Horman
2014-12-08  1:36 ` John Fastabend
2014-12-08  3:47   ` Simon Horman [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=20141208034715.GA606@vergenet.net \
    --to=simon.horman@netronome.com \
    --cc=john.r.fastabend@intel.com \
    --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).