From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Ravi Kerur <rkerur@gmail.com>, dpdk-dev <dev@dpdk.org>,
Harini Ramakrishnan <harini.ramakrishnan@microsoft.com>
Subject: Re: [dpdk-dev] [PATCH v2] Move common functions in eal_thread.c
Date: Fri, 11 Jan 2019 15:22:33 +0000 [thread overview]
Message-ID: <c2f140ad-5ddc-3fd1-3a43-5b7553c1bc4a@intel.com> (raw)
In-Reply-To: <1939756.e9X1pBQo5z@xps>
On 12/19/2018 9:20 PM, Thomas Monjalon wrote:
> 19/12/2018 22:09, Ferruh Yigit:
>> This patch is sitting on patchwork since 2015, I am updating it as rejected, if
>> it is still relevant please let us know.
>
> Most of the functions in lib/librte_eal/bsdapp/eal/eal_thread.c
> and lib/librte_eal/linuxapp/eal/eal_thread.c are the same.
> We must merge them before creating a third identical version for Windows.
How to manage this? Should we create a Bugzilla defect for it?
next prev parent reply other threads:[~2019-01-11 15:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 20:46 Ravi Kerur
2018-12-19 21:09 ` Ferruh Yigit
2018-12-19 21:20 ` Thomas Monjalon
2019-01-11 15:22 ` Ferruh Yigit [this message]
2019-01-11 17:51 ` Thomas Monjalon
2019-01-11 21:44 ` Ferruh Yigit
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=c2f140ad-5ddc-3fd1-3a43-5b7553c1bc4a@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=harini.ramakrishnan@microsoft.com \
--cc=rkerur@gmail.com \
--cc=thomas@monjalon.net \
/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).