From: Thomas Monjalon <thomas@monjalon.net>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org, remy.horton@intel.com
Subject: Re: [dpdk-dev] [PATCH] ethdev: fix meson build
Date: Fri, 27 Apr 2018 11:10:05 +0200 [thread overview]
Message-ID: <1731887.5Djbua2iTl@xps> (raw)
In-Reply-To: <20180427090103.158725-1-ferruh.yigit@intel.com>
27/04/2018 11:01, Ferruh Yigit:
> kvargs dependency added to ehtdev which is not updated in meson build
>
> Fixes: 9d5c2725ed8c ("ethdev: add common devargs parser")
> Cc: remy.horton@intel.com
>
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
Ack
I guess you want to squash it in next-net?
next prev parent reply other threads:[~2018-04-27 9:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 9:01 Ferruh Yigit
2018-04-27 9:10 ` Thomas Monjalon [this message]
2018-04-27 9:25 ` Ferruh Yigit
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=1731887.5Djbua2iTl@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=remy.horton@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).