From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Heinrich Kuhn <heinrich.kuhn@netronome.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] maintainers: update for nfp
Date: Wed, 3 Feb 2021 10:03:21 +0000 [thread overview]
Message-ID: <c1933033-5929-81f5-1500-827bcf1bb6f7@intel.com> (raw)
In-Reply-To: <e8c74084-efa7-529a-8804-5d271f315aa7@intel.com>
On 2/1/2021 7:56 PM, Ferruh Yigit wrote:
> On 1/31/2021 10:36 AM, Heinrich Kuhn wrote:
>> Release-on-close has been implemented for the NFP PMD. Remove the
>> UNMAINTAINED flag.
>>
>> Signed-off-by: Heinrich Kuhn <heinrich.kuhn@netronome.com>
>> ---
>> MAINTAINERS | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 77a2273c1..68c5ce6e5 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -815,7 +815,7 @@ F: drivers/net/nfb/
>> F: doc/guides/nics/nfb.rst
>> F: doc/guides/nics/features/nfb.ini
>> -Netronome nfp - UNMAINTAINED
>> +Netronome nfp
>> M: Heinrich Kuhn <heinrich.kuhn@netronome.com>
>> F: drivers/net/nfp/
>> F: doc/guides/nics/nfp.rst
>>
>
> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
Applied to dpdk-next-net/main, thanks.
next prev parent reply other threads:[~2021-02-03 10:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-31 10:36 Heinrich Kuhn
2021-02-01 19:56 ` Ferruh Yigit
2021-02-03 10:03 ` Ferruh Yigit [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-03-25 12:01 [dpdk-dev] [PATCH] maintainers: update for NFP heinrich.kuhn
2022-03-29 9:18 ` Thomas Monjalon
2021-08-23 8:29 heinrich.kuhn
2021-08-31 15:56 ` Ferruh Yigit
2020-02-11 12:23 Heinrich Kuhn
2020-02-15 14:42 ` 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=c1933033-5929-81f5-1500-827bcf1bb6f7@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=heinrich.kuhn@netronome.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).