From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org, Ivan Malov <ivan.malov@arknetworks.am>
Cc: Ferruh Yigit <ferruh.yigit@amd.com>, Andy Moreton <andy.moreton@amd.com>
Subject: Re: [PATCH] mailmap: update contributor entry
Date: Sat, 22 Jul 2023 11:21:52 +0200 [thread overview]
Message-ID: <9060397.5OynTdThKG@thomas> (raw)
In-Reply-To: <f905c451-0adf-072f-f42e-bfd639b47449@arknetworks.am>
We did not hear about Andy.
It's probably better to update within his next patch.
20/07/2023 18:55, Ivan Malov:
> PING
>
> On Tue, 13 Jun 2023, Ivan Malov wrote:
>
> > Signed-off-by: Ivan Malov <ivan.malov at arknetworks.am>
> > ---
> > .mailmap | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/.mailmap b/.mailmap
> > index 8e3940a253..d97cdc670c 100644
> > --- a/.mailmap
> > +++ b/.mailmap
> > @@ -105,7 +105,7 @@ Andriy Berestovskyy <aber at semihalf.com>
> > <andriy.berestovskyy at caviumnetworks.com>
> > Andrzej Ostruszka <amo at semihalf.com> <aostruszka at marvell.com>
> > Andy Gospodarek <andrew.gospodarek at broadcom.com> <gospo at broadcom.com>
> > Andy Green <andy at warmcat.com>
> > -Andy Moreton <amoreton at xilinx.com> <amoreton at solarflare.com>
> > +Andy Moreton <andy.moreton at amd.com> <amoreton at xilinx.com> <amoreton at
> > solarflare.com>
> > Andy Pei <andy.pei at intel.com>
> > Anirudh Venkataramanan <anirudh.venkataramanan at intel.com>
> > Ankur Dwivedi <adwivedi at marvell.com> <ankur.dwivedi at caviumnetworks.com>
> > <ankur.dwivedi at cavium.com>
next prev parent reply other threads:[~2023-07-22 9:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 14:03 Ivan Malov
2023-07-20 16:55 ` Ivan Malov
2023-07-22 9:21 ` Thomas Monjalon [this message]
2023-07-24 11:12 ` Andy Moreton
2023-07-24 13:14 ` Thomas Monjalon
-- strict thread matches above, loose matches on Subject: below --
2023-01-24 11:08 Viacheslav Galaktionov
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=9060397.5OynTdThKG@thomas \
--to=thomas@monjalon.net \
--cc=andy.moreton@amd.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=ivan.malov@arknetworks.am \
/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).