From: "Hunt, David" <david.hunt@intel.com>
To: "Gosiewski, LukaszX" <lukaszx.gosiewski@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Krakowiak, LukaszX" <lukaszx.krakowiak@intel.com>
Subject: Re: [dpdk-dev] [PATCH v3] power: update for handling fifo path string
Date: Tue, 16 Apr 2019 08:16:04 +0000 [thread overview]
Message-ID: <3F5BA2D9419A984DBB40DB5CFACBB36D20877FCF@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <20190416070258.19900-1-lukaszx.gosiewski@intel.com>
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.
next prev parent reply other threads:[~2019-04-16 8:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 11:52 [PATCH] power: update for handling fifo path string Lukasz Krakowiak
2019-04-15 7:33 ` [dpdk-dev] [PATCH v2 1/3] " Lukasz Gosiewski
2019-04-15 10:01 ` [dpdk-dev] [PATCH v3] " Lukasz Gosiewski
2019-04-15 15:50 ` Hunt, David
2019-04-16 7:02 ` Lukasz Gosiewski
2019-04-16 8:16 ` Hunt, David [this message]
2019-04-16 8:19 ` Krakowiak, LukaszX
2019-04-16 8:23 ` Gosiewski, LukaszX
2019-04-16 16:17 ` Ferruh Yigit
2019-04-16 10:20 ` [dpdk-dev] [PATCH v4] " Lukasz Gosiewski
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=3F5BA2D9419A984DBB40DB5CFACBB36D20877FCF@IRSMSX108.ger.corp.intel.com \
--to=david.hunt@intel.com \
--cc=dev@dpdk.org \
--cc=lukaszx.gosiewski@intel.com \
--cc=lukaszx.krakowiak@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.