From: Stephen Hemminger <stephen@networkplumber.org>
To: Yang Ming <ming.1.yang@nokia-sbell.com>
Cc: Anatoly Burakov <anatoly.burakov@intel.com>,
dev@dpdk.org, stable@dpdk.org
Subject: Re: [PATCH] eal/linux: enhance ASLR verification
Date: Wed, 12 Mar 2025 09:22:16 -0700 [thread overview]
Message-ID: <20250312092216.2c3ddb6f@hermes.local> (raw)
In-Reply-To: <20250228094405.1437-1-ming.1.yang@nokia-sbell.com>
On Fri, 28 Feb 2025 17:44:04 +0800
Yang Ming <ming.1.yang@nokia-sbell.com> wrote:
> @@ -26,7 +27,6 @@
> #include <numa.h>
> #include <numaif.h>
> #endif
> -
> #include <rte_errno.h>
> #include <rte_log.h>
> #include <rte_memory.h>
Best to keep blank line there
next prev parent reply other threads:[~2025-03-12 16:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-28 9:44 Yang Ming
2025-03-10 21:43 ` Stephen Hemminger
2025-03-12 3:13 ` Yang Ming
2025-03-12 16:29 ` Stephen Hemminger
2025-03-13 5:52 ` [External] " Yang Ming
2025-03-12 16:22 ` Stephen Hemminger [this message]
2025-03-13 6:19 ` [PATCH v2] eal/linux: improve ASLR check Yang Ming
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=20250312092216.2c3ddb6f@hermes.local \
--to=stephen@networkplumber.org \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=ming.1.yang@nokia-sbell.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).