From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Nicolau, Radu" <radu.nicolau@intel.com>,
"Marchand, David" <david.marchand@redhat.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
"Wu, Jingjing" <jingjing.wu@intel.com>,
"Xing, Beilei" <beilei.xing@intel.com>,
"Doherty, Declan" <declan.doherty@intel.com>,
"Sinha, Abhijit" <abhijit.sinha@intel.com>
Subject: RE: [PATCH] net/iavf: fix indent in Tx path
Date: Mon, 30 Oct 2023 00:16:12 +0000 [thread overview]
Message-ID: <DM4PR11MB5994695F1CFC67F46748F409D7A1A@DM4PR11MB5994.namprd11.prod.outlook.com> (raw)
In-Reply-To: <42c12ea7-efb8-b5d4-f5cf-20745f3c61d3@intel.com>
> -----Original Message-----
> From: Radu Nicolau <radu.nicolau@intel.com>
> Sent: Thursday, October 26, 2023 5:34 PM
> To: Marchand, David <david.marchand@redhat.com>; dev@dpdk.org
> Cc: stable@dpdk.org; Wu, Jingjing <jingjing.wu@intel.com>; Xing, Beilei
> <beilei.xing@intel.com>; Doherty, Declan <declan.doherty@intel.com>;
> Sinha, Abhijit <abhijit.sinha@intel.com>
> Subject: Re: [PATCH] net/iavf: fix indent in Tx path
>
>
> On 26-Oct-23 9:06 AM, David Marchand wrote:
> > Fix confusing indentations.
> >
> > Fixes: 1e728b01120c ("net/iavf: rework Tx path")
> > Fixes: 6bc987ecb860 ("net/iavf: support IPsec inline crypto")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: David Marchand <david.marchand@redhat.com>
> > ---
> > drivers/net/iavf/iavf_rxtx.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/net/iavf/iavf_rxtx.c
> > b/drivers/net/iavf/iavf_rxtx.c index c6ef6af1d8..cba7ec3564 100644
> > --- a/drivers/net/iavf/iavf_rxtx.c
> > +++ b/drivers/net/iavf/iavf_rxtx.c
> > @@ -2896,7 +2896,7 @@ iavf_xmit_pkts(void *tx_queue, struct rte_mbuf
> **tx_pkts, uint16_t nb_pkts)
> > txe->last_id = desc_idx_last;
> > desc_idx = txe->next_id;
> > txe = txn;
> > - }
> > + }
> >
> > if (nb_desc_ipsec) {
> > volatile struct iavf_tx_ipsec_desc *ipsec_desc = @@ -
> 2909,7
> > +2909,7 @@ iavf_xmit_pkts(void *tx_queue, struct rte_mbuf **tx_pkts,
> uint16_t nb_pkts)
> > if (txe->mbuf) {
> > rte_pktmbuf_free_seg(txe->mbuf);
> > txe->mbuf = NULL;
> > - }
> > + }
> >
> > iavf_fill_ipsec_desc(ipsec_desc, ipsec_md, &ipseclen);
> >
> Acked-by: Radu Nicolau <radu.nicolau@intel.com>
Applied to dpdk-next-net-intel.
Thanks
Qi
prev parent reply other threads:[~2023-10-30 0:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 8:06 David Marchand
2023-10-26 9:34 ` Radu Nicolau
2023-10-30 0:16 ` Zhang, Qi Z [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=DM4PR11MB5994695F1CFC67F46748F409D7A1A@DM4PR11MB5994.namprd11.prod.outlook.com \
--to=qi.z.zhang@intel.com \
--cc=abhijit.sinha@intel.com \
--cc=beilei.xing@intel.com \
--cc=david.marchand@redhat.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=radu.nicolau@intel.com \
--cc=stable@dpdk.org \
/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).