From: Thomas Monjalon <thomas@monjalon.net>
To: Ciara Power <ciara.power@intel.com>, Kevin Laatz <kevin.laatz@intel.com>
Cc: dev@dpdk.org, bruce.richardson@intel.com
Subject: Re: [dpdk-dev] [PATCH] maintainers: update for telemetry
Date: Thu, 25 Mar 2021 17:44:31 +0100 [thread overview]
Message-ID: <7103413.KdaQheqjef@thomas> (raw)
In-Reply-To: <b30a980f-8bfe-bed9-745a-773383956c50@intel.com>
25/03/2021 15:10, Kevin Laatz:
> On 25/03/2021 11:53, Ciara Power wrote:
> > Replace Kevin Laatz with Ciara Power.
> >
> > Signed-off-by: Ciara Power <ciara.power@intel.com>
> > ---
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > Telemetry - EXPERIMENTAL
> > -M: Kevin Laatz <kevin.laatz@intel.com>
> > +M: Ciara Power <ciara.power@intel.com>
>
> Acked-by: Kevin Laatz <kevin.laatz@intel.com>
Applied
prev parent reply other threads:[~2021-03-25 16:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 11:53 Ciara Power
2021-03-25 14:10 ` Kevin Laatz
2021-03-25 16:44 ` 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=7103413.KdaQheqjef@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=ciara.power@intel.com \
--cc=dev@dpdk.org \
--cc=kevin.laatz@intel.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).