From: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
To: Yuanhan Liu <yliu@fridaylinux.org>,
Santosh Shukla <santosh.shukla@caviumnetworks.com>,
dpdk stable <stable@dpdk.org>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [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 14:26:46 +0530 [thread overview]
Message-ID: <20180129085644.upqdfuo7vbxnfrmg@Pavan-LT> (raw)
In-Reply-To: <20180126160029.GH29540@yliu-mob>
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.
Regards,
Pavan.
>
> error: ‘rte_octeontx_pchan_map ’ undeclared (first use in this function)
>
> This patch is then dropped. If you think it's needed for 17.11.1 LTS
> release, please do a backport. And sorry for the late notice: it was
> my fault, I should have done the build before sending it out.
>
> --yliu
> >
> > Thanks.
> >
> > --yliu
> >
> > ---
> > >From 3ab8effa1fd5b07c88688ff14e816e0a314d7778 Mon Sep 17 00:00:00 2001
> > From: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
> > Date: Tue, 19 Dec 2017 23:31:45 +0530
> > Subject: [PATCH] event/octeontx: fix Rx adapter port id mapping
> >
> > [ upstream commit 9b4298339652c5f4c3a1391ed26caa5bbb26c158 ]
> >
> > When octeontx event dev receives a packet for the event Rx adapter, the
> > mbuf port id should contain the appropriate ethdev id instead of
> > internal channel info.
> >
> > Fixes: 45a914c5bd71 ("event/octeontx: support event Rx adapter")
> >
> > Signed-off-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
> > Acked-by: Santosh Shukla <santosh.shukla@caviumnetworks.com>
> > ---
next parent reply other threads:[~2018-01-29 8:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1516808026-25523-1-git-send-email-yliu@fridaylinux.org>
[not found] ` <1516808026-25523-72-git-send-email-yliu@fridaylinux.org>
[not found] ` <20180126160029.GH29540@yliu-mob>
2018-01-29 8:56 ` Pavan Nikhilesh [this message]
2018-01-29 14:44 Yuanhan Liu
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=20180129085644.upqdfuo7vbxnfrmg@Pavan-LT \
--to=pbhagavatula@caviumnetworks.com \
--cc=dev@dpdk.org \
--cc=santosh.shukla@caviumnetworks.com \
--cc=stable@dpdk.org \
--cc=yliu@fridaylinux.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).