DPDK patches and discussions
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Rami Rosen <ramirose@gmail.com>, dev@dpdk.org
Cc: stable@dpdk.org, tiwei.bie@intel.com, zhihong.wang@intel.com,
	yuanhan.liu@linux.intel.com
Subject: Re: [dpdk-dev] [PATCH] examples/vhost: remove unnecessary MAX_PRINT_BUFF defintion
Date: Mon, 10 Sep 2018 15:30:48 +0200	[thread overview]
Message-ID: <327adae3-0474-b4ae-ce7d-3d7d24a943d0@redhat.com> (raw)
In-Reply-To: <20180825192240.6503-1-ramirose@gmail.com>



On 08/25/2018 09:22 PM, Rami Rosen wrote:
> This patch removes an unnecessary definition of MAX_PRINT_BUFF
> in examples/vhost/main.c, since it is no longer being used.
> 
> Fixes: 68363d85857d ("examples/vhost: remove the non-working zero copy code").
> 
> Signed-off-by: Rami Rosen <ramirose@gmail.com>
> ---
>   examples/vhost/main.c | 3 ---
>   1 file changed, 3 deletions(-)
> 
> diff --git a/examples/vhost/main.c b/examples/vhost/main.c
> index 2175c1186..5d28d03f6 100644
> --- a/examples/vhost/main.c
> +++ b/examples/vhost/main.c
> @@ -58,9 +58,6 @@
>   /* Max number of devices. Limited by vmdq. */
>   #define MAX_DEVICES 64
>   
> -/* Size of buffers used for snprintfs. */
> -#define MAX_PRINT_BUFF 6072
> -
>   /* Maximum long option length for option parsing. */
>   #define MAX_LONG_OPT_SZ 64
>   
> 

Applied to dpdk-next-virtio/master, with changing the title to
pass check-git-log.sh script.

Thanks,
Maxime

      parent reply	other threads:[~2018-09-10 13:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-25 19:22 Rami Rosen
2018-08-30  4:40 ` Tiwei Bie
2018-09-10 13:30 ` Maxime Coquelin [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=327adae3-0474-b4ae-ce7d-3d7d24a943d0@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=dev@dpdk.org \
    --cc=ramirose@gmail.com \
    --cc=stable@dpdk.org \
    --cc=tiwei.bie@intel.com \
    --cc=yuanhan.liu@linux.intel.com \
    --cc=zhihong.wang@intel.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).