From: Thomas Monjalon <thomas@monjalon.net>
To: Liron Himi <lironh@marvell.com>
Cc: dev@dpdk.org, Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
dpdk-dev <dev@dpdk.org>, dpdk stable <stable@dpdk.org>,
Jerin Jacob <jerinjacobk@gmail.com>
Subject: Re: [dpdk-dev] [EXT] Re: [PATCH] config: update Marvell ARMADA
Date: Thu, 06 Feb 2020 15:01:06 +0100 [thread overview]
Message-ID: <9944341.zapYfy813O@xps> (raw)
In-Reply-To: <CALBAE1OO3T7mZPynkVV64uy6uQGPRkVQtEdo5fzGaNjLcpeFkg@mail.gmail.com>
23/01/2020 11:01, Jerin Jacob:
> On Mon, Dec 2, 2019 at 1:03 PM Jerin Jacob <jerinjacobk@gmail.com> wrote:
> >
> > On Mon, Dec 2, 2019 at 4:01 PM Liron Himi <lironh@marvell.com> wrote:
> > >
> > > Hi Jerin,
> > >
> > > I have created a patch to MUSDK that fix this conflicts as you suggested.
> > > This will be externally available in the next MUSDK release.
> > > Once it will be out, we can simplify the armada-config, but until then if anyone want to build DPDK with MUSDK it either needs this patch or compile MUSDK as shared lib
> >
> > Good that it is fixed in the library. +1 for this patch as short terms
> > solution till next MUSDK releases shows up.
>
> With the above note,
>
> Acked-by: Jerin Jacob <jerinj@marvell.com>
Applied, thanks
prev parent reply other threads:[~2020-02-06 14:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-29 9:11 [dpdk-dev] [PATCH] config: update Marvell ARMADA lironh
2019-11-29 14:05 ` Jerin Jacob
2019-11-29 19:00 ` [dpdk-dev] [EXT] " Liron Himi
2019-12-02 4:11 ` Jerin Jacob
2019-12-02 6:32 ` Liron Himi
2019-12-02 7:01 ` Liron Himi
2019-12-02 7:33 ` Jerin Jacob
2020-01-23 10:01 ` Jerin Jacob
2020-02-06 14:01 ` Thomas Monjalon [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=9944341.zapYfy813O@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=jerinjacobk@gmail.com \
--cc=lironh@marvell.com \
--cc=stable@dpdk.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.