From: Andrew Rybchenko <arybchenko@solarflare.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>, <dev@dpdk.org>,
David Hunt <david.hunt@intel.com>
Cc: Igor Romanov <igor.romanov@oktetlabs.ru>
Subject: Re: [dpdk-dev] [PATCH] examples/vm_power: fix build
Date: Mon, 14 Oct 2019 13:10:39 +0300 [thread overview]
Message-ID: <7e7415b6-d2cd-cf4c-8030-81c6a30b994c@solarflare.com> (raw)
In-Reply-To: <20191014100350.30226-1-ferruh.yigit@intel.com>
On 10/14/19 1:03 PM, Ferruh Yigit wrote:
> Fixes: 70febdcfd60f ("examples: check status of getting MAC address")
>
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
Thanks Ferruh, it is consequences of vm_power_manager
excluded from build because of missing libvirt dependency and
our inattentiveness when checking build results.
next prev parent reply other threads:[~2019-10-14 10:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-14 10:03 Ferruh Yigit
2019-10-14 10:10 ` Andrew Rybchenko [this message]
2019-10-14 10:17 ` Ferruh Yigit
2019-10-22 13:13 ` Bruce Richardson
2019-10-23 14:28 ` Thomas Monjalon
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=7e7415b6-d2cd-cf4c-8030-81c6a30b994c@solarflare.com \
--to=arybchenko@solarflare.com \
--cc=david.hunt@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=igor.romanov@oktetlabs.ru \
/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).