DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: "Hunt, David" <david.hunt@intel.com>
Cc: dev@dpdk.org, Marcin Hajkowski <marcinx.hajkowski@intel.com>
Subject: Re: [dpdk-dev] [PATCH v5 0/4] bidirect guest channel
Date: Thu, 04 Jul 2019 21:55:43 +0200	[thread overview]
Message-ID: <2275520.U60SUyaAjW@xps> (raw)
In-Reply-To: <2979557.O6mRKbeG0h@xps>

24/04/2019 10:44, Thomas Monjalon:
> 24/04/2019 10:38, Hunt, David:
> > On 22/4/2019 9:36 PM, Thomas Monjalon wrote:
> > > 05/04/2019 15:24, Hajkowski:
> > >> From: Marcin Hajkowski <marcinx.hajkowski@intel.com>
> > >>
> > >> Extend guest channel API to allow bidirectional
> > >> communication. Modify power manager host and guest
> > >> side to communicate in both directions.
> > > This patchset is deferred to 19.08 because of a lack
> > > of review.
> > >
> > > Note: too many librte_power patches are not reviewed.
> > 
> > 
> > Hi Thomas,
> > 
> >   The four remaining patch sets for power were initially submitted after 
> > the v1 deadline, and were not expected to make it into 19.05. We will be 
> > sure to review for 19.08.
> 
> OK thanks for the confirmation.
> In such case, it is better to add "19.08" in the subject prefix
> so it is explicit from the beginning. Thanks

There was no more review since April.
I guess it will miss 19.08 as well.



      parent reply	other threads:[~2019-07-04 19:55 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-05 13:24 Hajkowski
2019-04-05 13:24 ` Hajkowski
2019-04-05 13:24 ` [dpdk-dev] [PATCH v5 1/4] power: fix invalid socket indicator value Hajkowski
2019-04-05 13:24   ` Hajkowski
2019-09-27  8:42   ` [dpdk-dev] [PATCH v6 0/4] bidirectional guest channel Marcin Hajkowski
2019-09-27  8:42     ` [dpdk-dev] [PATCH v6 1/4] power: fix invalid socket indicator value Marcin Hajkowski
2019-09-27  8:42     ` [dpdk-dev] [PATCH v6 2/4] power: extend guest channel API for reading Marcin Hajkowski
2019-09-27  8:42     ` [dpdk-dev] [PATCH v6 3/4] power: process incoming confirmation cmds Marcin Hajkowski
2019-09-27  8:42     ` [dpdk-dev] [PATCH v6 4/4] power: send confirmation cmd to vm guest Marcin Hajkowski
2019-10-27 18:29     ` [dpdk-dev] [PATCH v6 0/4] bidirectional guest channel Thomas Monjalon
2019-04-05 13:24 ` [dpdk-dev] [PATCH v5 2/4] power: extend guest channel API for reading Hajkowski
2019-04-05 13:24   ` Hajkowski
2019-09-26 13:00   ` Hunt, David
2019-09-26 15:53     ` Daly, Lee
2019-04-05 13:24 ` [dpdk-dev] [PATCH v5 3/4] power: process incoming confirmation cmds Hajkowski
2019-04-05 13:24   ` Hajkowski
2019-09-26 13:01   ` Hunt, David
2019-09-26 15:49     ` Daly, Lee
2019-04-05 13:24 ` [dpdk-dev] [PATCH v5 4/4] power: send confirmation cmd to vm guest Hajkowski
2019-04-05 13:24   ` Hajkowski
2019-09-26 13:06   ` Hunt, David
2019-09-26 15:47     ` Daly, Lee
2019-04-22 20:36 ` [dpdk-dev] [PATCH v5 0/4] bidirect guest channel Thomas Monjalon
2019-04-22 20:36   ` Thomas Monjalon
2019-04-24  8:38   ` Hunt, David
2019-04-24  8:38     ` Hunt, David
2019-04-24  8:44     ` Thomas Monjalon
2019-04-24  8:44       ` Thomas Monjalon
2019-07-04 19:55       ` 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=2275520.U60SUyaAjW@xps \
    --to=thomas@monjalon.net \
    --cc=david.hunt@intel.com \
    --cc=dev@dpdk.org \
    --cc=marcinx.hajkowski@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).