From: Stephen Hemminger <stephen@networkplumber.org>
To: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Cc: Bruce Richardson <bruce.richardson@intel.com>,
dev@dpdk.org, Reshma Pattan <reshma.pattan@intel.com>,
Aman Singh <aman.deep.singh@intel.com>,
Naga Harish K S V <s.v.naga.harish.k@intel.com>,
Kishore Padmanabha <kishore.padmanabha@broadcom.com>,
Ajit Khaparde <ajit.khaparde@broadcom.com>,
Nithin Dabilpuram <ndabilpuram@marvell.com>,
Kiran Kumar K <kirankumark@marvell.com>,
Sunil Kumar Kori <skori@marvell.com>,
Satha Rao <skoteshwar@marvell.com>,
Harman Kalra <hkalra@marvell.com>,
Anatoly Burakov <anatoly.burakov@intel.com>,
Cristian Dumitrescu <cristian.dumitrescu@intel.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [RFC] ethdev: add buffer size parameter to rte_eth_dev_get_name_by_port()
Date: Thu, 9 Apr 2026 08:23:58 -0700 [thread overview]
Message-ID: <20260409082358.1cddcf06@phoenix.local> (raw)
In-Reply-To: <445dc90b-081a-4ab0-bd3f-924557dcac9a@oktetlabs.ru>
On Thu, 9 Apr 2026 12:05:35 +0300
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru> wrote:
> >>
> >> As far as I know typically variable declaration and code are not mixed
> >> in DPDK.
> >>
> >
> > AFAIK That used to be the case because early versions of DPDK targetting a
> > very early C standard. More recently, we've started allowing this sort of
> > use, which makes the code more readable IMHO and easier to work with too as
> > commenting out blocks when debugging leads to fewer unused variable warnings.
> >
> > /Bruce
>
> Bruce, thanks for the clarification.
I started doing this more to avoid uninitalized variable hazards.
next prev parent reply other threads:[~2026-04-09 15:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 1:36 [RFC] ethdev: add buffer size parameter to rte_eth_dev_get_name_by_port() Stephen Hemminger
2026-04-09 6:59 ` Andrew Rybchenko
2026-04-09 7:58 ` Bruce Richardson
2026-04-09 9:05 ` Andrew Rybchenko
2026-04-09 15:23 ` Stephen Hemminger [this message]
2026-05-29 0:07 ` [PATCH v2] " Stephen Hemminger
2026-06-02 20:53 ` Stephen Hemminger
2026-06-03 2:20 ` Stephen Hemminger
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=20260409082358.1cddcf06@phoenix.local \
--to=stephen@networkplumber.org \
--cc=ajit.khaparde@broadcom.com \
--cc=aman.deep.singh@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=bruce.richardson@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=hkalra@marvell.com \
--cc=kirankumark@marvell.com \
--cc=kishore.padmanabha@broadcom.com \
--cc=ndabilpuram@marvell.com \
--cc=reshma.pattan@intel.com \
--cc=s.v.naga.harish.k@intel.com \
--cc=skori@marvell.com \
--cc=skoteshwar@marvell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.