From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Morten Brørup" <mb@smartsharesystems.com>,
"Olivier Matz" <olivier.matz@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] FW: [PATCH] librte_net: define TCP flags in rte_tcp.h instead of in rte_eth_ctrl.h
Date: Fri, 10 May 2019 10:40:57 +0100 [thread overview]
Message-ID: <ed7bd562-e609-2b11-9970-c39f7e62d5e6@intel.com> (raw)
In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35B42838@smartserver.smartshare.dk>
On 5/10/2019 8:01 AM, Morten Brørup wrote:
> Hi Olivier,
>
> I submitted the below patch about a month ago, and nothing happened. The patch is simple and obvious. Is something wrong with it, or did I not follow the submission process correctly?
Hi Morten,
I don't see this mail in mail list (and list archive), or in my inbox (it looks
like I am in cc in original mail).
Something may be went wrong in your side while sending, can you please send the
patch again?
>
>
> Med venlig hilsen / kind regards
>
> Morten Brørup
> CTO
>
>
> SmartShare Systems A/S
> Tonsbakken 16-18
> DK-2740 Skovlunde
> Denmark
>
> Office +45 70 20 00 93
> Direct +45 89 93 50 22
> Mobile +45 25 40 82 12
>
> mb@smartsharesystems.com
> www.smartsharesystems.com
> -----Original Message-----
> From: Morten Brørup [mailto:mb@smartsharesystems.com]
> Sent: Friday, April 5, 2019 11:55 AM
> To: olivier.matz@6wind.com; thomas@monjalon.net; ferruh.yigit@intel.com; arybchenko@solarflare.com
> Cc: dev@dpdk.org; Morten Brørup
> Subject: [PATCH] librte_net: define TCP flags in rte_tcp.h instead of in rte_eth_ctrl.h
>
> Signed-off-by: Morten Brørup <mb@smartsharesystems.com>
<...>
next prev parent reply other threads:[~2019-05-10 9:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 7:01 Morten Brørup
2019-05-10 7:01 ` Morten Brørup
2019-05-10 9:40 ` Ferruh Yigit [this message]
2019-05-10 9:40 ` Ferruh Yigit
2019-05-10 13:46 ` Morten Brørup
2019-05-10 13:46 ` Morten Brørup
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=ed7bd562-e609-2b11-9970-c39f7e62d5e6@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=mb@smartsharesystems.com \
--cc=olivier.matz@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).