DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: David Marchand <david.marchand@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2 0/3] remove limit on devargs parameters length
Date: Wed, 18 Feb 2015 13:44:32 +0100	[thread overview]
Message-ID: <1613668.yGLTTCiIDO@xps13> (raw)
In-Reply-To: <1423839795-29450-1-git-send-email-david.marchand@6wind.com>

2015-02-13 16:03, David Marchand:
> Here is a little patchset that removes the limit on the devargs parameters
> length. Previously, arguments specified by user would be stored in a static
> buffer, while there is no particular reason why we should have such a
> constraint, afaik.
> 
> Changes since v1:
> - fix devargs tests (problem reported by Thomas)
> 
> David Marchand (3):
>   devargs: indent and cleanup
>   devargs: remove limit on parameters length
>   app/test: fix devargs tests

Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>

Applied, thanks

      parent reply	other threads:[~2015-02-18 12:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-07 13:03 [dpdk-dev] [PATCH 0/2] " David Marchand
2015-01-07 13:03 ` [dpdk-dev] [PATCH 1/2] devargs: indent and cleanup David Marchand
2015-01-07 13:03 ` [dpdk-dev] [PATCH 2/2] devargs: remove limit on parameters length David Marchand
2015-01-07 22:59   ` Stephen Hemminger
2015-01-08  8:19     ` David Marchand
2015-01-08  9:15     ` Panu Matilainen
2015-02-13 15:03 ` [dpdk-dev] [PATCH v2 0/3] remove limit on devargs " David Marchand
2015-02-13 15:03   ` [dpdk-dev] [PATCH v2 1/3] devargs: indent and cleanup David Marchand
2015-02-13 15:03   ` [dpdk-dev] [PATCH v2 2/3] devargs: remove limit on parameters length David Marchand
2015-02-13 15:03   ` [dpdk-dev] [PATCH v2 3/3] app/test: fix devargs tests David Marchand
2015-02-18 12:44   ` 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=1613668.yGLTTCiIDO@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=david.marchand@6wind.com \
    --cc=dev@dpdk.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).