From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Gosiewski, LukaszX" <lukaszx.gosiewski@intel.com>,
"Krakowiak, LukaszX" <lukaszx.krakowiak@intel.com>,
"Hunt, David" <david.hunt@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 17:17:45 +0100 [thread overview]
Message-ID: <344fb66d-f046-3891-f5b2-965c995e98fc@intel.com> (raw)
In-Reply-To: <F0DEA83DFA04F547B47BD0778ECAB2204FBE0E@HASMSX110.ger.corp.intel.com>
On 4/16/2019 9:23 AM, Gosiewski, LukaszX wrote:
> Hi,
> Could there be also possibility, that patch is on hold because it's still waiting for moderator approval?
> I got this mail when posting:
> " Your mail to 'dev' with the subject
>
> [PATCH v3] power: update for handling fifo path string
>
> Is being held until the list moderator can review it for approval.
>
> The reason it is being held:
>
> Post by non-member to a members-only list"
It was on host because of above reason, you need to subscribe to the mail list.
>
> Lukasz
>
> -----Original Message-----
> From: Krakowiak, LukaszX
> Sent: Tuesday, April 16, 2019 10:20 AM
> To: Hunt, David <david.hunt@intel.com>; Gosiewski, LukaszX <lukaszx.gosiewski@intel.com>
> Cc: dev@dpdk.org
> Subject: RE: [PATCH v3] power: update for handling fifo path string
>
> 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.
>
next prev parent reply other threads:[~2019-04-16 16:17 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
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 [this message]
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=344fb66d-f046-3891-f5b2-965c995e98fc@intel.com \
--to=ferruh.yigit@intel.com \
--cc=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 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).