From: Kalesh Anakkur Purayil <kalesh-anakkur.purayil@broadcom.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dpdk-dev <dev@dpdk.org>,
Ajit Kumar Khaparde <ajit.khaparde@broadcom.com>
Subject: Re: [dpdk-dev] [PATCH] net/bnxt: drop the unused attribute
Date: Thu, 29 Apr 2021 09:50:10 +0530 [thread overview]
Message-ID: <CAH-L+nMbSiBsskONPSKsx+Wgp1VQeuhjCiMv-S2whdBVmFeELQ@mail.gmail.com> (raw)
In-Reply-To: <786e27d5-0fdd-8346-623a-8419b718a239@intel.com>
[-- Attachment #1: Type: text/plain, Size: 949 bytes --]
Hi Ferruh,
On Wed, Apr 28, 2021 at 9:18 PM Ferruh Yigit <ferruh.yigit@intel.com> wrote:
> On 4/23/2021 6:22 AM, Kalesh A P wrote:
> > From: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
> >
> > Remove "__rte_unused" instances that are wrongly marked.
> >
>
> Can you please provide the fixes tags, so that patch can be backported to
> required stable versions?
>
[Kalesh]: I was not sure whether it qualifies as a fix. That's why I didn't
add it in the first place.
Below is the fixes tags:
Fixes: 6dc83230b43b ("net/bnxt: support port representor data path")
Fixes: 1bf01f5135f8 ("net/bnxt: prevent device access when device is in
reset")
Cc: stable@dpdk.org
Do you want me to send a new version?
Regards,
Kalesh
>
> > Signed-off-by: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
> > Reviewed-by: Somnath Kotur <somnath.kotur@broadcom.com>
> > Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
>
> <...>
>
--
Regards,
Kalesh A P
next prev parent reply other threads:[~2021-04-29 4:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 5:22 Kalesh A P
2021-04-24 19:23 ` Ajit Khaparde
2021-04-28 15:48 ` Ferruh Yigit
2021-04-29 4:20 ` Kalesh Anakkur Purayil [this message]
2021-04-29 11:08 ` Ferruh Yigit
2021-04-29 11:37 ` Kalesh Anakkur Purayil
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=CAH-L+nMbSiBsskONPSKsx+Wgp1VQeuhjCiMv-S2whdBVmFeELQ@mail.gmail.com \
--to=kalesh-anakkur.purayil@broadcom.com \
--cc=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.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).