From: Yuanhan Liu <yliu@fridaylinux.org>
To: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
Cc: Santosh Shukla <santosh.shukla@caviumnetworks.com>,
dpdk stable <stable@dpdk.org>,
dev@dpdk.org
Subject: Re: [dpdk-stable] patch 'event/octeontx: fix Rx adapter port id mapping' has been queued to LTS release 17.11.1
Date: Mon, 29 Jan 2018 22:44:44 +0800 [thread overview]
Message-ID: <20180129144444.GM29540@yliu-mob> (raw)
On Mon, Jan 29, 2018 at 02:26:46PM +0530, Pavan Nikhilesh wrote:
> Hi Yliu,
>
> On Sat, Jan 27, 2018 at 12:00:29AM +0800, Yuanhan Liu wrote:
> > On Wed, Jan 24, 2018 at 11:32:20PM +0800, Yuanhan Liu wrote:
> > > Hi,
> > >
> > > FYI, your patch has been queued to LTS release 17.11.1
> > >
> > > Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet.
> > > It will be pushed if I get no objections before 01/26/18. So please
> > > shout if anyone has objections.
> >
> > I met an build error with this one:
>
> This is due to map file having improper tag i.e.
>
> http://dpdk.org/dev/patchwork/patch/32510/
>
> +
> +DPDK_18.04 {
>
> Fixed while applying.
>
> + global:
> +
> + rte_octeontx_pchan_map;
> +
> +};
>
> Ferruh fixed it while applying.
Hi Pavan,
Not really. The reason it failed to build is this patch is targeted for
stable release while it references above symbol that introduced in another
patch that will not be cherry-picked to stable release.
So could you do a backport, without introducing above external symbol?
I'm wondering you could hide it internally?
DPDK_18.04 won't exist for v17.11.1 after all.
Thanks.
--yliu
next reply other threads:[~2018-01-29 14:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 14:44 Yuanhan Liu [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-01-24 15:31 [dpdk-stable] patch 'kni: fix build with kernel 4.15' " Yuanhan Liu
2018-01-24 15:32 ` [dpdk-stable] patch 'event/octeontx: fix Rx adapter port id mapping' " Yuanhan Liu
2018-01-26 16:00 ` Yuanhan Liu
2018-01-29 8:56 ` Pavan Nikhilesh
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=20180129144444.GM29540@yliu-mob \
--to=yliu@fridaylinux.org \
--cc=dev@dpdk.org \
--cc=pbhagavatula@caviumnetworks.com \
--cc=santosh.shukla@caviumnetworks.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 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).