DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Krakowiak, LukaszX" <lukaszx.krakowiak@intel.com>
To: "Hunt, David" <david.hunt@intel.com>,
	"Gosiewski, LukaszX" <lukaszx.gosiewski@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v3] power: update for handling fifo path string
Date: Tue, 16 Apr 2019 08:19:51 +0000	[thread overview]
Message-ID: <DC695E1BE92F754CA2AE786BE043D81318DE0EFD@hasmsx107.ger.corp.intel.com> (raw)
Message-ID: <20190416081951.9YkSTV6NS4JRmOIHcPHNJl1anBafvYljlhjet6KdnaI@z> (raw)
In-Reply-To: <3F5BA2D9419A984DBB40DB5CFACBB36D20877FCF@IRSMSX108.ger.corp.intel.com>

Hi,

On Friday Lukasz sent patch: [PATCH v2 1/3] power: update for handling fifo path string.
But this was mistake, it should be the one patch, and I suppose this lock the newer versions of this patches.

Lukasz

-----Original Message-----
From: Hunt, David 
Sent: Tuesday, April 16, 2019 10:16 AM
To: Gosiewski, LukaszX <lukaszx.gosiewski@intel.com>
Cc: dev@dpdk.org; Krakowiak, LukaszX <lukaszx.krakowiak@intel.com>
Subject: RE: [PATCH v3] power: update for handling fifo path string

Hi Lukasz, 

-----Original Message-----
From: Gosiewski, LukaszX 
Sent: Tuesday, 16 April, 2019 8:03 AM
To: Hunt, David <david.hunt@intel.com>
Cc: dev@dpdk.org; Krakowiak, LukaszX <lukaszx.krakowiak@intel.com>; Gosiewski, LukaszX <lukaszx.gosiewski@intel.com>
Subject: [PATCH v3] power: update for handling fifo path string

From: Lukasz Krakowiak <lukaszx.krakowiak@intel.com>

Removed doubled created fifo path string for channel info.

---
v3:
*improvement to coding style

v2:
* rebase to master changes

Signed-off-by: Lukasz Krakowiak <lukaszx.krakowiak@intel.com>
Signed-off-by: Lukasz Gosiewski <lukaszx.gosiewski@intel.com>
---

This patch is still not appearing in patchwork. It may be because the "Signed-off" tags are below the first '---'.
Could you post up as v4?

Rgds,
Dave.

  parent reply	other threads:[~2019-04-16  8:19 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-03 11:52 [dpdk-dev] [PATCH] " Lukasz Krakowiak
2019-04-03 11:52 ` Lukasz Krakowiak
2019-04-15  7:33 ` [dpdk-dev] [PATCH v2 1/3] " Lukasz Gosiewski
2019-04-15  7:33   ` Lukasz Gosiewski
2019-04-15 10:01 ` [dpdk-dev] [PATCH v3] " Lukasz Gosiewski
2019-04-15 10:01   ` Lukasz Gosiewski
2019-04-15 15:50   ` Hunt, David
2019-04-15 15:50     ` Hunt, David
2019-04-16  7:02 ` Lukasz Gosiewski
2019-04-16  7:02   ` Lukasz Gosiewski
2019-04-16  8:16   ` Hunt, David
2019-04-16  8:16     ` Hunt, David
2019-04-16  8:19     ` Krakowiak, LukaszX [this message]
2019-04-16  8:19       ` Krakowiak, LukaszX
2019-04-16  8:23       ` Gosiewski, LukaszX
2019-04-16  8:23         ` Gosiewski, LukaszX
2019-04-16 16:17         ` Ferruh Yigit
2019-04-16 16:17           ` Ferruh Yigit
2019-04-16 10:20 ` [dpdk-dev] [PATCH v4] " Lukasz Gosiewski
2019-04-16 10:20   ` Lukasz Gosiewski
2019-04-17 12:21   ` Hunt, David
2019-04-17 12:21     ` Hunt, David
2019-07-04 20:06     ` 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=DC695E1BE92F754CA2AE786BE043D81318DE0EFD@hasmsx107.ger.corp.intel.com \
    --to=lukaszx.krakowiak@intel.com \
    --cc=david.hunt@intel.com \
    --cc=dev@dpdk.org \
    --cc=lukaszx.gosiewski@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).