DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Cc: dev@dpdk.org, "ferruh.yigit@intel.com" <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [EXT] Re: [PATCH] eal: change init macro as exec environment specific
Date: Tue, 02 Apr 2019 14:45:32 +0200	[thread overview]
Message-ID: <1774374.xfdjkiLUGA@xps> (raw)
In-Reply-To: <fd8b784e4470dad617c636f5d0e517ba0ce4e2e2.camel@marvell.com>

02/04/2019 03:15, Jerin Jacob Kollanukkaran:
> On Thu, 2019-03-14 at 20:44 +0000, Jerin Jacob Kollanukkaran wrote:
> > On Wed, 2019-03-13 at 14:14 +0530, Jerin Jacob wrote:
> > > On Wed, 2019-03-13 at 09:16 +0100, Thomas Monjalon wrote:
> > > > Then maybe you should send your patches so we can decide if it is
> > > > maintainable enough or not.
> > > 
> > > The  __attribute__((constructor)) only stuff we have issue to
> > > support.
> > > The common code changes are related to adapt
> > > __attribute__((constructor)) scheme.
> > > 
> > > This patch will fix that issue. Other than that there is no common
> > > code
> > > changes.i.e everything emulated under lib/librte_eal/new_port/
> > 
> > Thomas,
> > 
> > I explained the use case and changes required. Let me know, do you
> > need
> > any other change on this patch to get this patch accepted?
> 
> Ping?

This patch needs to be refreshed.
And I have some comments, sending in another email with better context.

  parent reply	other threads:[~2019-04-02 12:45 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-07 12:04 [dpdk-dev] " Jerin Jacob
2017-10-11 13:02 ` Thomas Monjalon
2017-10-11 14:33   ` Jerin Jacob
2019-03-01 17:05     ` Ferruh Yigit
2019-03-01 17:16       ` Ferruh Yigit
2019-03-01 17:28       ` Thomas Monjalon
2019-03-12 19:25         ` [dpdk-dev] [EXT] " Jerin Jacob Kollanukkaran
2019-03-12 20:33           ` Thomas Monjalon
2019-03-13  8:02             ` Jerin Jacob Kollanukkaran
2019-03-13  8:16               ` Thomas Monjalon
2019-03-13  8:44                 ` Jerin Jacob Kollanukkaran
2019-03-14 20:44                   ` Jerin Jacob Kollanukkaran
2019-03-14 20:44                     ` Jerin Jacob Kollanukkaran
2019-04-02  1:15                     ` Jerin Jacob Kollanukkaran
2019-04-02  1:15                       ` Jerin Jacob Kollanukkaran
2019-04-02 12:45                       ` Thomas Monjalon [this message]
2019-04-02 12:45                         ` Thomas Monjalon
2019-04-02 12:57     ` [dpdk-dev] " Thomas Monjalon
2019-04-02 12:57       ` Thomas Monjalon
2019-04-02 13:20       ` Wiles, Keith
2019-04-02 13:20         ` Wiles, Keith
2019-04-03 19:28 ` [dpdk-dev] [PATCH v2] " Jerin Jacob Kollanukkaran
2019-04-03 19:28   ` Jerin Jacob Kollanukkaran
2019-04-03 20:07   ` Thomas Monjalon
2019-04-03 20:07     ` Thomas Monjalon
2019-04-03 21:52     ` Thomas Monjalon
2019-04-03 21:52       ` 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=1774374.xfdjkiLUGA@xps \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=jerinj@marvell.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).