DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Ori Kam <orika@mellanox.com>
Cc: dev@dpdk.org, adrien.mazarguil@6wind.com, john.mcnamara@intel.com
Subject: Re: [dpdk-dev] [PATCH 1/2] examples/flow_filtering: demo of simple rte flow
Date: Wed, 25 Oct 2017 12:35:24 +0200	[thread overview]
Message-ID: <1840091.2XWlWDJWeC@xps> (raw)
In-Reply-To: <1508408108-8672-1-git-send-email-orika@mellanox.com>

Hi,

19/10/2017 12:15, Ori Kam:
>  examples/flow_filtering/Makefile      |  17 +++
>  examples/flow_filtering/flow_blocks.c | 150 +++++++++++++++++++++
>  examples/flow_filtering/main.c        | 244 ++++++++++++++++++++++++++++++++++

You must add this example in examples/Makefile.

You must also add an entry in the MAINTAINERS file.

You can probably squash this patch with the doc patch.

> --- /dev/null
> +++ b/examples/flow_filtering/flow_blocks.c
> @@ -0,0 +1,150 @@
> +/*-
> + *   BSD LICENSE
> + *
> + *   Copyright 2017 Mellanox.
> + *
> + *   Redistribution and use in source and binary forms, with or without
> + *   modification, are permitted provided that the following conditions
> + *   are met:
> + *
> + *     * Redistributions of source code must retain the above copyright
> + *       notice, this list of conditions and the following disclaimer.
> + *     * Redistributions in binary form must reproduce the above copyright
> + *       notice, this list of conditions and the following disclaimer in
> + *       the documentation and/or other materials provided with the
> + *       distribution.
> + *     * Neither the name of 6WIND S.A. nor the names of its

I guess you mean Mellanox here.

      reply	other threads:[~2017-10-25 10:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-19 10:15 Ori Kam
2017-10-25 10:35 ` Thomas Monjalon [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=1840091.2XWlWDJWeC@xps \
    --to=thomas@monjalon.net \
    --cc=adrien.mazarguil@6wind.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=orika@mellanox.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).