DPDK patches and discussions
 help / color / mirror / Atom feed
From: Phil Yang <Phil.Yang@arm.com>
To: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
Cc: Ruifeng Wang <Ruifeng.Wang@arm.com>,
	"david.marchand@redhat.com" <david.marchand@redhat.com>,
	"thomas@monjalon.net" <thomas@monjalon.net>, nd <nd@arm.com>,
	nd <nd@arm.com>
Subject: Re: [dpdk-dev] [PATCH] maintainers: update for MCS lock
Date: Fri, 9 Oct 2020 01:19:25 +0000	[thread overview]
Message-ID: <DB7PR08MB3865E94A5CE7F5B88BC483A3E9080@DB7PR08MB3865.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <20201008231359.33704-1-honnappa.nagarahalli@arm.com>

Honnappa Nagarahalli <honnappa.nagarahalli@arm.com> wrote:
 
> Subject: [PATCH] maintainers: update for MCS lock
> 
> Updating MAINTAINERS file for MCS lock.
> 
> Signed-off-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>

Thank you, Honnappa.
Acked-by: Phil Yang <phil.yang@arm.com>


> ---
> Phil Yang is leaving Arm. I worked with Phil on the MCS lock design and
> have done the reviews in the past for the implementation.
> 
>  MAINTAINERS | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 75a17d51c..2a18262d6 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -238,7 +238,7 @@ F: lib/librte_eal/include/rte_bitmap.h
>  F: app/test/test_bitmap.c
> 
>  MCSlock
> -M: Phil Yang <phil.yang@arm.com>
> +M: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
>  F: lib/librte_eal/include/generic/rte_mcslock.h
>  F: app/test/test_mcslock.c
> 
> --
> 2.17.1


  reply	other threads:[~2020-10-09  1:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-08 23:13 Honnappa Nagarahalli
2020-10-09  1:19 ` Phil Yang [this message]
2020-10-09  9:05   ` 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=DB7PR08MB3865E94A5CE7F5B88BC483A3E9080@DB7PR08MB3865.eurprd08.prod.outlook.com \
    --to=phil.yang@arm.com \
    --cc=Honnappa.Nagarahalli@arm.com \
    --cc=Ruifeng.Wang@arm.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=nd@arm.com \
    --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).