From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Stephen Hemminger <stephen@networkplumber.org>, dev@dpdk.org
Cc: Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [PATCH 1/3] MAINTAINERS: add maintainer for TAP device
Date: Mon, 4 Mar 2024 16:03:45 +0000 [thread overview]
Message-ID: <18c28d3d-c744-4474-8166-cc5c45549dbd@amd.com> (raw)
In-Reply-To: <20240229173154.121491-2-stephen@networkplumber.org>
On 2/29/2024 5:31 PM, Stephen Hemminger wrote:
> Add myself as maintainer for TAP device.
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
>
Acked-by: Ferruh Yigit <ferruh.yigit@amd.com>
next prev parent reply other threads:[~2024-03-04 16:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 17:31 [PATCH 0/3] TAP device fixes Stephen Hemminger
2024-02-29 17:31 ` [PATCH 1/3] MAINTAINERS: add maintainer for TAP device Stephen Hemminger
2024-03-04 16:03 ` Ferruh Yigit [this message]
2024-02-29 17:31 ` [PATCH 2/3] net/tap: do not overwrite rte_flow errors Stephen Hemminger
2024-02-29 17:31 ` [PATCH 3/3] net/tap: compute TC handle correctly Stephen Hemminger
2024-03-04 17:45 ` [PATCH 0/3] TAP device fixes Ferruh Yigit
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=18c28d3d-c744-4474-8166-cc5c45549dbd@amd.com \
--to=ferruh.yigit@amd.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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).