From: Jerin Jacob <jerinjacobk@gmail.com>
To: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Cc: Volodymyr Fialko <vfialko@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
Akhil Goyal <gakhil@marvell.com>,
Anoob Joseph <anoobj@marvell.com>
Subject: Re: [PATCH] app/testeventdev: fix limit names in error message
Date: Mon, 7 Nov 2022 19:40:46 +0530 [thread overview]
Message-ID: <CALBAE1M=UCaD3ZHxW1wTB+nEFZ0LdkwrWeMdi59yhk2-tqNphQ@mail.gmail.com> (raw)
In-Reply-To: <PH0PR18MB40862B9A327EBCB0E5A5396DDE389@PH0PR18MB4086.namprd18.prod.outlook.com>
On Thu, Nov 3, 2022 at 9:02 PM Pavan Nikhilesh Bhagavatula
<pbhagavatula@marvell.com> wrote:
>
>
>
> > -----Original Message-----
> > From: Volodymyr Fialko <vfialko@marvell.com>
> > Sent: Monday, October 31, 2022 4:09 PM
> > To: dev@dpdk.org
> > Cc: Jerin Jacob Kollanukkaran <jerinj@marvell.com>; Akhil Goyal
> > <gakhil@marvell.com>; Anoob Joseph <anoobj@marvell.com>; Pavan
> > Nikhilesh Bhagavatula <pbhagavatula@marvell.com>; Volodymyr Fialko
> > <vfialko@marvell.com>
> > Subject: [PATCH] app/testeventdev: fix limit names in error message
> >
> > Swap min and max values to match their labels.
> >
> > Fixes: 2eaa37b8663 ("app/eventdev: add vector mode in pipeline test")
> >
> > Signed-off-by: Volodymyr Fialko <vfialko@marvell.com>
>
> Acked-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
Applied to dpdk-next-net-eventdev/for-main. Thanks
>
> > ---
> > app/test-eventdev/test_pipeline_common.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/app/test-eventdev/test_pipeline_common.c b/app/test-
> > eventdev/test_pipeline_common.c
> > index ab39046ce7..5229d74fe0 100644
> > --- a/app/test-eventdev/test_pipeline_common.c
> > +++ b/app/test-eventdev/test_pipeline_common.c
> > @@ -534,8 +534,8 @@ pipeline_event_rx_adapter_setup(struct evt_options
> > *opt, uint8_t stride,
> > if (opt->vector_size < limits.min_sz ||
> > opt->vector_size > limits.max_sz) {
> > evt_err("Vector size [%d] not within limits
> > max[%d] min[%d]",
> > - opt->vector_size, limits.min_sz,
> > - limits.max_sz);
> > + opt->vector_size, limits.max_sz,
> > + limits.min_sz);
> > return -EINVAL;
> > }
> >
> > --
> > 2.25.1
>
prev parent reply other threads:[~2022-11-07 14:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 10:39 Volodymyr Fialko
2022-11-03 15:32 ` Pavan Nikhilesh Bhagavatula
2022-11-07 14:10 ` Jerin Jacob [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='CALBAE1M=UCaD3ZHxW1wTB+nEFZ0LdkwrWeMdi59yhk2-tqNphQ@mail.gmail.com' \
--to=jerinjacobk@gmail.com \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=jerinj@marvell.com \
--cc=pbhagavatula@marvell.com \
--cc=vfialko@marvell.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).