From: Jerin Jacob <jerinjacobk@gmail.com>
To: "Jayatheerthan, Jay" <jay.jayatheerthan@intel.com>
Cc: Volodymyr Fialko <vfialko@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>, Jerin Jacob <jerinj@marvell.com>,
"Rao, Nikhil" <nikhil.rao@intel.com>,
"gakhil@marvell.com" <gakhil@marvell.com>,
"anoobj@marvell.com" <anoobj@marvell.com>,
"Gujjar, Abhinandan S" <abhinandan.gujjar@intel.com>
Subject: Re: [PATCH] eventdev: fix name of Rx conf type
Date: Wed, 28 Sep 2022 16:33:34 +0530 [thread overview]
Message-ID: <CALBAE1NNf3gvg6Nj5Ojx91cMR6eyk_Vb0NaciiEDGd1duKDM8g@mail.gmail.com> (raw)
In-Reply-To: <DM6PR11MB4348676540BE98489C806833FD529@DM6PR11MB4348.namprd11.prod.outlook.com>
On Mon, Sep 26, 2022 at 7:38 PM Jayatheerthan, Jay
<jay.jayatheerthan@intel.com> wrote:
>
> Looks good to me. Thanks for catching this one!
>
> Acked-by: Jay Jayatheerthan <jay.jayatheerthan@intel.com>
Updated the git commit as follows and applied to
dpdk-next-net-eventdev/for-main. Thanks
eventdev: fix name of Rx conf type in documentation
Rename configuration structure type to correspond definition.
Fixes: dcc806c2638 ("eventdev: add eth Rx adapter API")
Cc: stable@dpdk.org
Signed-off-by: Volodymyr Fialko <vfialko@marvell.com>
Acked-by: Jay Jayatheerthan <jay.jayatheerthan@intel.com>
>
>
> > -----Original Message-----
> > From: Volodymyr Fialko <vfialko@marvell.com>
> > Sent: Monday, September 26, 2022 5:28 PM
> > To: dev@dpdk.org; Jayatheerthan, Jay <jay.jayatheerthan@intel.com>; Jerin Jacob <jerinj@marvell.com>; Rao, Nikhil
> > <nikhil.rao@intel.com>
> > Cc: gakhil@marvell.com; anoobj@marvell.com; Gujjar, Abhinandan S <abhinandan.gujjar@intel.com>; Volodymyr Fialko
> > <vfialko@marvell.com>
> > Subject: [PATCH] eventdev: fix name of Rx conf type
> >
> > Rename configuration structure type to correspond definition.
> >
> > Fixes: dcc806c2638 ("eventdev: add eth Rx adapter API")
> >
> > Signed-off-by: Volodymyr Fialko <vfialko@marvell.com>
> > ---
> > lib/eventdev/rte_event_eth_rx_adapter.h | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/lib/eventdev/rte_event_eth_rx_adapter.h b/lib/eventdev/rte_event_eth_rx_adapter.h
> > index a3313c8d32..a9fdeb7b45 100644
> > --- a/lib/eventdev/rte_event_eth_rx_adapter.h
> > +++ b/lib/eventdev/rte_event_eth_rx_adapter.h
> > @@ -458,7 +458,7 @@ int rte_event_eth_rx_adapter_free(uint8_t id);
> > * @see RTE_EVENT_ETH_RX_ADAPTER_CAP_MULTI_EVENTQ
> > *
> > * @param conf
> > - * Additional configuration structure of type *rte_event_eth_rx_adapter_conf*
> > + * Additional configuration structure of type *rte_event_eth_rx_adapter_queue_conf*
> > *
> > * @return
> > * - 0: Success, Receive queue added correctly.
> > --
> > 2.25.1
>
prev parent reply other threads:[~2022-09-28 11:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 11:58 Volodymyr Fialko
2022-09-26 14:08 ` Jayatheerthan, Jay
2022-09-28 11:03 ` 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=CALBAE1NNf3gvg6Nj5Ojx91cMR6eyk_Vb0NaciiEDGd1duKDM8g@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=abhinandan.gujjar@intel.com \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=jay.jayatheerthan@intel.com \
--cc=jerinj@marvell.com \
--cc=nikhil.rao@intel.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).