From: "Singh, Jasvinder" <jasvinder.singh@intel.com>
To: "Ajmera, Megha" <megha.ajmera@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
Subject: RE: [PATCH] sched: Fix subport profile id not set correctly.
Date: Thu, 18 Aug 2022 09:32:44 +0000 [thread overview]
Message-ID: <CY4PR11MB15892DE4F1CF00911CA3DBD6E06D9@CY4PR11MB1589.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220818060315.1454280-1-megha.ajmera@intel.com>
> -----Original Message-----
> From: Ajmera, Megha <megha.ajmera@intel.com>
> Sent: Thursday, August 18, 2022 7:03 AM
> To: dev@dpdk.org; Singh, Jasvinder <jasvinder.singh@intel.com>;
> Dumitrescu, Cristian <cristian.dumitrescu@intel.com>
> Subject: [PATCH] sched: Fix subport profile id not set correctly.
>
> In rte_sched_subport_config() API, subport_profile_id is not set correctly.
>
> Signed-off-by: Megha Ajmera <megha.ajmera@intel.com>
> ---
> lib/sched/rte_sched.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/lib/sched/rte_sched.c b/lib/sched/rte_sched.c index
> 599c7e9536..09f855a04b 100644
> --- a/lib/sched/rte_sched.c
> +++ b/lib/sched/rte_sched.c
> @@ -1263,8 +1263,6 @@ rte_sched_subport_config(struct rte_sched_port
> *port,
>
> n_subports++;
>
> - subport_profile_id = 0;
> -
> /* Port */
> port->subports[subport_id] = s;
>
> --
> 2.25.1
When fixing a bug, it is required to reference the id of the commit which introduced the bug, also CCed to the stable@dpdk.org. Guidelines on preparing and sending bug fix patch are available @ https://doc.dpdk.org/guides/contributing/patches.html
prev parent reply other threads:[~2022-08-18 9:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 6:03 Megha Ajmera
2022-08-18 9:32 ` Singh, Jasvinder [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=CY4PR11MB15892DE4F1CF00911CA3DBD6E06D9@CY4PR11MB1589.namprd11.prod.outlook.com \
--to=jasvinder.singh@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=megha.ajmera@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).