DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Wang, Haiyue" <haiyue.wang@intel.com>
To: "Yigit, Ferruh" <ferruh.yigit@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Thomas Monjalon <thomas@monjalon.net>,
	Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Subject: RE: [PATCH v1] ethdev: beautify the Rx desc number check indent
Date: Tue, 15 Feb 2022 11:41:16 +0000	[thread overview]
Message-ID: <BYAPR11MB34959B584C8794260BF5F219F7349@BYAPR11MB3495.namprd11.prod.outlook.com> (raw)
In-Reply-To: <c2192289-47d5-bc3a-44f9-419567bb47df@intel.com>

> -----Original Message-----
> From: Yigit, Ferruh <ferruh.yigit@intel.com>
> Sent: Tuesday, February 15, 2022 17:20
> To: Wang, Haiyue <haiyue.wang@intel.com>; dev@dpdk.org
> Cc: Thomas Monjalon <thomas@monjalon.net>; Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
> Subject: Re: [PATCH v1] ethdev: beautify the Rx desc number check indent
> 
> On 2/15/2022 7:04 AM, Haiyue Wang wrote:
> > Align to Tx desc number check indent, which may help to understand Rx
> > descriptor limits member in the alignment comparison view. And remove
> > the extra empty line.
> >
> > Signed-off-by: Haiyue Wang <haiyue.wang@intel.com>
> > ---
> >   lib/ethdev/rte_ethdev.c | 5 ++---
> >   1 file changed, 2 insertions(+), 3 deletions(-)
> >
> > diff --git a/lib/ethdev/rte_ethdev.c b/lib/ethdev/rte_ethdev.c
> > index 70c850a2f1..54f1e14c6b 100644
> > --- a/lib/ethdev/rte_ethdev.c
> > +++ b/lib/ethdev/rte_ethdev.c
> > @@ -1799,9 +1799,8 @@ rte_eth_rx_queue_setup(uint16_t port_id, uint16_t rx_queue_id,
> >   	}
> >
> >   	if (nb_rx_desc > dev_info.rx_desc_lim.nb_max ||
> > -			nb_rx_desc < dev_info.rx_desc_lim.nb_min ||
> > -			nb_rx_desc % dev_info.rx_desc_lim.nb_align != 0) {
> > -
> > +	    nb_rx_desc < dev_info.rx_desc_lim.nb_min ||
> > +	    nb_rx_desc % dev_info.rx_desc_lim.nb_align != 0) {
> >   		RTE_ETHDEV_LOG(ERR,
> >   			"Invalid value for nb_rx_desc(=%hu), should be: <= %hu, >= %hu, and a product
> of %hu\n",
> >   			nb_rx_desc, dev_info.rx_desc_lim.nb_max,
> 
> Hi Haiyue,
> 
> Initial code matches to DPDK coding convention, updated code doesn't:
> https://doc.dpdk.org/guides/contributing/coding_style.html

I just read that 'rte_eth_tx_queue_setup' does it as above. ;-)

> 
> And I don't think syntax only updates are good idea,
> it corrupts the git history with minimal gain, instead
> better to fix them while doing a functional changes in
> those lines.

Got it.

      reply	other threads:[~2022-02-15 11:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-15  7:04 Haiyue Wang
2022-02-15  9:19 ` Ferruh Yigit
2022-02-15 11:41   ` Wang, Haiyue [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=BYAPR11MB34959B584C8794260BF5F219F7349@BYAPR11MB3495.namprd11.prod.outlook.com \
    --to=haiyue.wang@intel.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=thomas@monjalon.net \
    /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).