From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
Panu Matilainen <pmatilai@redhat.com>,
"Carew, Alan" <alan.carew@intel.com>,
"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] vm_power_manager uses channel_commands.h which is not placed in installed copy of DPDK
Date: Mon, 15 Feb 2016 18:03:32 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE202455038@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <2759253.A73iH2ao4l@xps13>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon
> Sent: Monday, February 15, 2016 1:21 PM
> To: Panu Matilainen <pmatilai@redhat.com>; Carew, Alan
> <alan.carew@intel.com>; De Lara Guarch, Pablo
> <pablo.de.lara.guarch@intel.com>
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] vm_power_manager uses channel_commands.h which is
> not placed in installed copy of DPDK
>
>
> > I can certainly submit a patch to disable it by default in the configs
> > (seems reasonable unmaintained code would default to off) and add a
> > deprecation note along the lines of "if no maintainer steps up, this
> > code will be removed in 16.07" if you like :)
>
> Before sending such notice, we should wait for comments of some known
> contributors to librte_power.
> Alan, Pablo, what is your opinion?
Hi,
We will look from a maintainer from the Intel DPDK team and try resolve the
open issues.
Regards,
John
prev parent reply other threads:[~2016-02-15 18:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-13 23:38 Matthew Hall
2016-02-15 8:29 ` Panu Matilainen
2016-02-15 10:15 ` Thomas Monjalon
2016-02-15 11:56 ` Panu Matilainen
2016-02-15 13:21 ` Thomas Monjalon
2016-02-15 18:03 ` Mcnamara, John [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=B27915DBBA3421428155699D51E4CFE202455038@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=alan.carew@intel.com \
--cc=dev@dpdk.org \
--cc=pablo.de.lara.guarch@intel.com \
--cc=pmatilai@redhat.com \
--cc=thomas.monjalon@6wind.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).