From: Stephen Hemminger <stephen@networkplumber.org>
To: Farhat Ullah <farhatullah.software.engr999@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH] doc: fixing name of rfc2697 and rfc2698
Date: Thu, 9 Jan 2025 20:24:00 -0800 [thread overview]
Message-ID: <20250109202400.4bd825aa@hermes.local> (raw)
In-Reply-To: <CAOE7cFB+U97a9ys6zHXFEKt=jEx+7ESCQkJgH7Crcjr0j2T1NQ@mail.gmail.com>
On Mon, 23 Dec 2024 22:00:08 +0500
Farhat Ullah <farhatullah.software.engr999@gmail.com> wrote:
> This patch fixes typos in the testpmd
> document for rfc2697 and rfc2698
>
> Signed-off-by: Farhat Ullah <farhatullah.software.engr999@gmail.com>
Looks like your mail system is corrupting plain text patches.
See patchwork for examples of how apply is failing
Please resubmit.
prev parent reply other threads:[~2025-01-10 4:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-23 17:00 Farhat Ullah
2025-01-10 4:24 ` 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=20250109202400.4bd825aa@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=farhatullah.software.engr999@gmail.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).