From: Stephen Hemminger <stephen@networkplumber.org>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, David Young <dave@youngcopy.com>
Subject: Re: [PATCH] maintainers: fix prog guide paths
Date: Sat, 28 Sep 2024 11:35:51 -0700 [thread overview]
Message-ID: <20240928113551.1c4589d8@hermes.local> (raw)
In-Reply-To: <20240925212237.1283476-1-thomas@monjalon.net>
On Wed, 25 Sep 2024 23:22:33 +0200
Thomas Monjalon <thomas@monjalon.net> wrote:
> When moving some files in doc subdirectories for ethdev and eventdev,
> the references in the file MAINTAINERS were forgotten.
> The new paths are used in this fix.
>
> Fixes: 41dd9a6bc2d9 ("doc: reorganize prog guide")
>
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
Acked-by: Stephen Hemminger <stephen@networkplumber.org>
next prev parent reply other threads:[~2024-09-28 18:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-25 21:22 Thomas Monjalon
2024-09-26 2:00 ` fengchengwen
2024-09-28 18:35 ` Stephen Hemminger [this message]
2024-09-28 19:52 ` Thomas Monjalon
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=20240928113551.1c4589d8@hermes.local \
--to=stephen@networkplumber.org \
--cc=dave@youngcopy.com \
--cc=dev@dpdk.org \
--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).