DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: dev <dev@dpdk.org>, Sachin Saxena <sachin.saxena@nxp.com>
Subject: Re: [dpdk-dev] [PATCH v2 1/2] config: remove redundant dpaa2 build
Date: Wed, 6 Nov 2019 21:58:09 +0100	[thread overview]
Message-ID: <CAJFAV8w7t4wRX6mAseSWbTwp-17ZFW70PWUaV5KBZZ4hoU_31w@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8xVCCRid1BVTxb1MmyTtkTZNTGDRK9xELNhaspZsxS99g@mail.gmail.com>

On Tue, Nov 5, 2019 at 10:17 AM David Marchand
<david.marchand@redhat.com> wrote:
> On Tue, Nov 5, 2019 at 9:05 AM Hemant Agrawal <hemant.agrawal@nxp.com> wrote:
> >
> > dpaa and dpaa2 config have evolved to be same. The same binary
> > can now work across the platforms. So, there is no need to maintain
> > two different build configs.
> > The dpaa config shall work for both generation of dpaa platforms.
> >
> > Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
> Reviewed-by: David Marchand <david.marchand@redhat.com>
>

Applied, thanks.


--
David Marchand


      reply	other threads:[~2019-11-06 20:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-04 11:21 [dpdk-dev] [PATCH " Hemant Agrawal
2019-11-04 11:21 ` [dpdk-dev] [PATCH 2/2] doc: bump the supported SDK and firmware version Hemant Agrawal
2019-11-04 20:48 ` [dpdk-dev] [PATCH 1/2] config: remove redundant dpaa2 build David Marchand
2019-11-05  3:41   ` Hemant Agrawal
2019-11-05  7:59 ` [dpdk-dev] [PATCH v2 " Hemant Agrawal
2019-11-05  7:59   ` [dpdk-dev] [PATCH v2 2/2] doc: bump the supported SDK and firmware version Hemant Agrawal
2019-11-05  9:17     ` David Marchand
2019-11-06 21:00       ` David Marchand
2019-11-05  9:17   ` [dpdk-dev] [PATCH v2 1/2] config: remove redundant dpaa2 build David Marchand
2019-11-06 20:58     ` David Marchand [this message]

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=CAJFAV8w7t4wRX6mAseSWbTwp-17ZFW70PWUaV5KBZZ4hoU_31w@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=sachin.saxena@nxp.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).