DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, Rajesh Kumar <rajesh3.kumar@intel.com>
Subject: Re: [PATCH] examples/ptp_tap_relay_sw: forbid shadowed variables
Date: Thu, 18 Jun 2026 13:05:54 -0700	[thread overview]
Message-ID: <20260618130554.616501bd@phoenix.local> (raw)
In-Reply-To: <20260618142526.191340-1-thomas@monjalon.net>

On Thu, 18 Jun 2026 16:25:26 +0200
Thomas Monjalon <thomas@monjalon.net> wrote:

> By removing the compilation flag no_shadow_cflag,
> it becomes forbidden to shadow a variable.
> 
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> ---

Thanks, example did not exist when the first pass was done.

Acked-by: Stephen Hemminger <stephen@networkplumber.org>

      reply	other threads:[~2026-06-18 20:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-18 14:25 [PATCH] examples/ptp_tap_relay_sw: forbid shadowed variables Thomas Monjalon
2026-06-18 20:05 ` 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=20260618130554.616501bd@phoenix.local \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=rajesh3.kumar@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