From: Stephen Hemminger <stephen@networkplumber.org>
To: zhichaox.zeng@intel.com
Cc: dev@dpdk.org, qiming.yang@intel.com, bruce.richardson@intel.com,
hkalra@marvell.com, david.marchand@redhat.com,
aconole@redhat.com, olivier.matz@6wind.com, thomas@monjalon.net,
stable@dpdk.org
Subject: Re: [PATCH v3] lib/eal: fix segfaults due to thread exit order
Date: Mon, 30 May 2022 09:26:45 -0700 [thread overview]
Message-ID: <20220530092645.31c9318d@hermes.local> (raw)
In-Reply-To: <20220530134738.488602-1-zhichaox.zeng@intel.com>
On Mon, 30 May 2022 13:47:38 +0000
zhichaox.zeng@intel.com wrote:
> +static void warn_parent(void)
> +{
> + RTE_LOG(WARNING, EAL, "fork() was called, DPDK won't work in the child "
> + "process unless it calls rte_eal_init()\n");
> +}
> +
Too wordy. Don't break messages across lines.
next prev parent reply other threads:[~2022-05-30 16:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 16:04 [DPDK] eal/linux: " zhichaox.zeng
2022-05-17 8:29 ` Morten Brørup
2022-05-17 15:25 ` [EXT] " Harman Kalra
2022-05-18 14:39 ` [DPDK v2] lib/eal: " zhichaox.zeng
2022-05-23 11:16 ` [PATCH " zhichaox.zeng
2022-05-23 12:10 ` David Marchand
2022-05-23 13:00 ` David Marchand
2022-05-30 13:47 ` [PATCH v3] " zhichaox.zeng
2022-05-30 16:26 ` Stephen Hemminger [this message]
2022-05-30 16:28 ` Stephen Hemminger
2022-06-02 8:21 ` Zeng, ZhichaoX
2022-06-07 10:14 ` Zeng, ZhichaoX
2022-06-15 6:01 ` [PATCH v4] " zhichaox.zeng
2022-06-24 1:42 ` Zeng, ZhichaoX
2022-06-24 7:50 ` David Marchand
2022-06-30 10:38 ` Zeng, ZhichaoX
2022-06-30 12:24 ` Bruce Richardson
2022-09-06 2:51 ` [PATCH v5] lib/eal: fix segfaults in exiting Zhichao Zeng
2022-09-06 15:03 ` Stephen Hemminger
2022-09-07 8:53 ` Zeng, ZhichaoX
2022-10-11 5:25 ` [PATCH v6] " Zhichao Zeng
2022-10-11 14:04 ` Stephen Hemminger
2022-10-19 1:51 ` Zeng, ZhichaoX
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=20220530092645.31c9318d@hermes.local \
--to=stephen@networkplumber.org \
--cc=aconole@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=hkalra@marvell.com \
--cc=olivier.matz@6wind.com \
--cc=qiming.yang@intel.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=zhichaox.zeng@intel.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).