From: Thomas Monjalon <thomas@monjalon.net>
To: "Morten Brørup" <mb@smartsharesystems.com>
Cc: dev@dpdk.org, Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [PATCH] stack: improve source code readability
Date: Tue, 13 Oct 2026 09:46:04 +0200 [thread overview]
Message-ID: <x9VW9oFbSESonugkbjgkCw@monjalon.net> (raw)
In-Reply-To: <20260811084835.7ca64d35@phoenix.local>
11/08/2026 17:48, Stephen Hemminger:
> On Tue, 11 Aug 2026 12:17:27 +0000
> Morten Brørup <mb@smartsharesystems.com> wrote:
>
> > Fixed misleading local variable names in the standard stack,
> > for improved source code readability.
> > No functional change.
> >
> > Fixes: 05d3b5283cc1 ("stack: introduce stack library")
> >
> > Signed-off-by: Morten Brørup <mb@smartsharesystems.com>
> > ---
>
> Makes sense, but drop Fixes since that implies it is a bug fix.
> Cleanups don't need fixes.
>
> Acked-by: Stephen Hemminger <stephen@networkplumber.org>
Applied without Fixes line, thanks.
prev parent reply other threads:[~2026-10-13 7:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 12:17 [PATCH] stack: improve source code readability Morten Brørup
2026-08-11 15:48 ` Stephen Hemminger
2026-10-13 7:46 ` Thomas Monjalon [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=x9VW9oFbSESonugkbjgkCw@monjalon.net \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=mb@smartsharesystems.com \
--cc=stephen@networkplumber.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