DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: Thomas Monjalon <thomas@monjalon.net>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] version: 18.05-rc0
Date: Wed, 21 Feb 2018 09:21:28 +0000	[thread overview]
Message-ID: <20180221092128.GA17160@bricha3-MOBL3.ger.corp.intel.com> (raw)
In-Reply-To: <DB3PR04MB0762AF99D3C82674FF1D47FE89CE0@DB3PR04MB0762.eurprd04.prod.outlook.com>

On Wed, Feb 21, 2018 at 08:16:07AM +0000, Hemant Agrawal wrote:
> Hi Bruce,
> 
> 
> > On Tue, Feb 20, 2018 at 06:12:49AM +0000, Hemant Agrawal wrote:
> > > Hi Thomas,
> > > 	Can you integrate ?
> > >
> > > An early integration will help the subsequent kernel module patches to use
> > new path.
> > >
> > > Regards,
> > > Hemant
> > >
> > 
> > I think that could do with a respin to include the meson.build file changes also.
> > 
> [Hemant]  I have just sent a v6. However,
> I was only able to test linux based igb_uio.ko compilation with meson.
> I could not find the kni build support with meson.

Yes, it's not implemented yet.
> 
> My freebsd meson compilation is failing. Will you please help in checking out the freebsd meson changes?

Yes, will do.

/Bruce

  reply	other threads:[~2018-02-21  9:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-19 20:55 Thomas Monjalon
2018-02-19 21:03 ` Thomas Monjalon
2018-02-20  6:12   ` Hemant Agrawal
2018-02-20  9:38     ` Bruce Richardson
2018-02-21  8:16       ` Hemant Agrawal
2018-02-21  9:21         ` Bruce Richardson [this message]
2018-02-20 18:00   ` Burakov, Anatoly

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=20180221092128.GA17160@bricha3-MOBL3.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.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).