From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: David Marchand <david.marchand@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 0/7] cleanup option parsing in bsd/linux eal
Date: Tue, 23 Sep 2014 17:37:04 +0200 [thread overview]
Message-ID: <1874814.lYLZLWNiOE@xps13> (raw)
In-Reply-To: <20140922124327.GD25406@hmsreliant.think-freely.org>
2014-09-22 08:43, Neil Horman:
> On Mon, Sep 22, 2014 at 10:37:54AM +0200, David Marchand wrote:
> > Following Neil comments, here is a patchset to rework the eal options parsing.
> > I tried to have everything common to linux and bsd in a single file.
> >
> > I ran a little make test on linux, it looks fine (at least I have as many fails
> > as before my changes).
> >
> > There is still work in this part, but I want to stop here.
> > If anyone wants to continue ... :-)
Yes, many eal parts should be factorized for Linux and BSD.
Cleanups are welcome!
> Series
> ACK
Applied
Thanks
--
Thomas
prev parent reply other threads:[~2014-09-23 15:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-22 8:37 David Marchand
2014-09-22 8:37 ` [dpdk-dev] [PATCH 1/7] eal: remove unused --use-device option David Marchand
2014-09-22 12:22 ` Neil Horman
2014-09-22 13:49 ` David Marchand
2014-09-22 8:37 ` [dpdk-dev] [PATCH 2/7] eal: factorise unsupported option handling David Marchand
2014-09-22 8:37 ` [dpdk-dev] [PATCH 3/7] eal: remove duplicate handling of white/black list David Marchand
2014-09-22 8:37 ` [dpdk-dev] [PATCH 4/7] eal: fix checkpatch issues before moving code David Marchand
2014-09-22 8:37 ` [dpdk-dev] [PATCH 5/7] eal: merge bsd and linux common options parsing David Marchand
2014-09-22 8:38 ` [dpdk-dev] [PATCH 6/7] eal: rework long " David Marchand
2014-09-22 12:42 ` Neil Horman
2014-09-22 8:38 ` [dpdk-dev] [PATCH 7/7] eal: indent files David Marchand
2014-09-22 12:43 ` [dpdk-dev] [PATCH 0/7] cleanup option parsing in bsd/linux eal Neil Horman
2014-09-23 15:37 ` 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=1874814.lYLZLWNiOE@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).