From: Stephen Hemminger <stephen@networkplumber.org>
To: Rahul Gupta <rahulgupt@linux.microsoft.com>
Cc: dev@dpdk.org, thomas@monjalon.net, bruce.richardson@intel.com,
dmitry.kozliuk@gmail.com, sovaradh@linux.microsoft.com,
okaya@kernel.org, sujithsankar@microsoft.com,
sowmini.varadhan@microsoft.com, krathinavel@microsoft.com,
rahulrgupta27@gmail.com, Rahul Gupta <rahulgupt@microsoft.com>
Subject: Re: [dpdk-dev] [PATCH] eal: refactor rte_eal_init into sub-functions
Date: Mon, 15 Jan 2024 09:01:32 -0800 [thread overview]
Message-ID: <20240115090132.26c659ce@hermes.local> (raw)
In-Reply-To: <1705308610-938-1-git-send-email-rahulgupt@linux.microsoft.com>
On Mon, 15 Jan 2024 00:50:10 -0800
Rahul Gupta <rahulgupt@linux.microsoft.com> wrote:
> + /* running on a slave lcore */
NAK
Do not add slave terminology back anywhere in DPDK
prev parent reply other threads:[~2024-01-15 17:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-15 8:50 Rahul Gupta
2024-01-15 17:01 ` Stephen Hemminger [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=20240115090132.26c659ce@hermes.local \
--to=stephen@networkplumber.org \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=krathinavel@microsoft.com \
--cc=okaya@kernel.org \
--cc=rahulgupt@linux.microsoft.com \
--cc=rahulgupt@microsoft.com \
--cc=rahulrgupta27@gmail.com \
--cc=sovaradh@linux.microsoft.com \
--cc=sowmini.varadhan@microsoft.com \
--cc=sujithsankar@microsoft.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).