From: Thomas Monjalon <thomas@monjalon.net>
To: "McDaniel, Timothy" <timothy.mcdaniel@intel.com>
Cc: stable@dpdk.org, "dev@dpdk.org" <dev@dpdk.org>,
"jerinj@marvell.com" <jerinj@marvell.com>,
"jerinjacobk@gmail.com" <jerinjacobk@gmail.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [PATCH v2 0/2] DLB2: cq_weight fixes
Date: Mon, 11 Jul 2022 22:30:54 +0200 [thread overview]
Message-ID: <11292509.ICPdZLu4VQ@thomas> (raw)
In-Reply-To: <SN6PR11MB31036E9461934534BE8FCEA49E829@SN6PR11MB3103.namprd11.prod.outlook.com>
08/07/2022 17:02, McDaniel, Timothy:
> From: Thomas Monjalon <thomas@monjalon.net>
> > 06/07/2022 23:46, Timothy McDaniel:
> > > This patch series contains the following:
> > > - fix coverity issue 379234
> > > - improve error reporting for cq_weight feature
> > >
> > > Changes since V1
> > > - fixed a repeated word in the commit message of patch 1
> > >
> > > Timothy McDaniel (2):
> > > event/dlb2: fix cq_weight array overflow
> > > event/dlb2: improve cq_weight error messages
> >
> > Should we merge those patches in 22.07-rc4? No risk?
>
> I see no risk in merging these changes. I retested with them, and one fixes a coverity issue.
Applied, thanks.
next prev parent reply other threads:[~2022-07-11 20:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220706213141.2374006-1-timothy.mcdaniel@intel.com>
2022-07-06 21:31 ` [PATCH 1/2] event/dlb2: fix cq_weight array overflow Timothy McDaniel
2022-07-06 21:46 ` [PATCH v2 0/2] DLB2: cq_weight fixes Timothy McDaniel
2022-07-06 21:46 ` [PATCH v2 1/2] event/dlb2: fix cq_weight array overflow Timothy McDaniel
2022-07-06 21:46 ` [PATCH v2 2/2] event/dlb2: improve cq_weight error messages Timothy McDaniel
2022-07-08 14:26 ` [PATCH v2 0/2] DLB2: cq_weight fixes Thomas Monjalon
2022-07-08 15:02 ` McDaniel, Timothy
2022-07-11 20:30 ` Thomas Monjalon [this message]
2022-07-11 20:33 ` McDaniel, Timothy
2022-07-06 21:31 ` [PATCH 2/2] event/dlb2: improve cq_weight error messages Timothy McDaniel
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=11292509.ICPdZLu4VQ@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=jerinjacobk@gmail.com \
--cc=stable@dpdk.org \
--cc=timothy.mcdaniel@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).