DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Ravi Kerur <rkerur@gmail.com>
Cc: dpdk-dev <dev@dpdk.org>, Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH v2] Move common functions in eal_thread.c
Date: Wed, 19 Dec 2018 21:09:24 +0000	[thread overview]
Message-ID: <dac52764-e838-a280-db19-da8354727b9c@intel.com> (raw)
In-Reply-To: <1440017166-1695-1-git-send-email-rkerur@gmail.com>

On 8/19/2015 9:46 PM, rkerur at gmail.com (Ravi Kerur) wrote:
> v2:
>    > Remove un-needed header file eal_private.h from freeBSD
>      eal_thread.c after code movement.
> 
> v1:
> Changes include
>    > Moving common functions in eal_thread.c in
>      linuxapp and bsdapp into common/eal_common_thread.c file.
>    > Rearrange eal_common_thread.c compilation in Makefile
>      for ABI.
> 
> Compiled successfully for following targets
>    > x86_64-native-linuxapp-clang
>    > x86_64-native-linuxapp-gcc
>    > x86_x32-native-linuxapp-gcc
>    > i686-native-linuxapp-gcc
>    > x86_64-native-bsdapp-clang
>    > x86_64-native-bsdapp-gcc
> 
> Tested on
>    > Ubuntu 14.04, testpmd functionality
>    > FreeBSD 10.1, testpmd functionality
> 
> Signed-off-by: Ravi Kerur <rkerur at gmail.com>

Hi Ravi,

This patch is sitting on patchwork since 2015, I am updating it as rejected, if
it is still relevant please let us know.

Sorry for any inconvenience caused.

  reply	other threads:[~2018-12-19 21:09 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 [this message]
2018-12-19 21:20   ` Thomas Monjalon
2019-01-11 15:22     ` Ferruh Yigit
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=dac52764-e838-a280-db19-da8354727b9c@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --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).