From: "Chautru, Nicolas" <nicolas.chautru@intel.com>
To: "trix@redhat.com" <trix@redhat.com>,
"thomas@monjalon.net" <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] maintainers: New Reviewer entry type added to MAINTAINERS
Date: Thu, 1 Oct 2020 21:22:26 +0000 [thread overview]
Message-ID: <BY5PR11MB445159A9135C8F09F0983FA3F8300@BY5PR11MB4451.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20201001143030.9194-1-trix@redhat.com>
Hi Tom,
Thanks for the help.
Note that they are a few other BBDEV patches in flight for 20.11 on top of the acc100 PMD that you may want to be aware of.
https://patches.dpdk.org/project/dpdk/list/?series=&submitter=chautru&state=&q=&archive=&delegate=
Acked-by: Nicolas Chautru <nicolas.chautru@intel.com>
> -----Original Message-----
> From: trix@redhat.com <trix@redhat.com>
> Sent: Thursday, October 1, 2020 7:31 AM
> To: thomas@monjalon.net; Chautru, Nicolas <nicolas.chautru@intel.com>
> Cc: dev@dpdk.org; Tom Rix <trix@redhat.com>
> Subject: [PATCH] maintainers: New Reviewer entry type added to
> MAINTAINERS
>
> From: Tom Rix <trix@redhat.com>
>
> Copied from the Linux kernel MAINTAINERS file.
> A Reviewer is designated person who wishes to review changes in areas of
> interest.
>
> Added self as Reviewer for baseband.
>
> I am a Linux kernel Reviewer for the fpga n3000/vista creek which has
> several bitstream based baseband devices. So I want to help out here as
> well.
>
> Signed-off-by: Tom Rix <trix@redhat.com>
> ---
> MAINTAINERS | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index c0abbe0fc..30faf2455 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -17,7 +17,8 @@ Descriptions of section entries:
> X: Files and directories exclusion, same rules as F:
> K: Keyword regex pattern to match content.
> One regex pattern per line. Multiple K: lines acceptable.
> -
> + R: Designated *Reviewer*: FullName <address@domain>
> + These reviewers should be CCed on patches.
>
> General Project Administration
> ------------------------------
> @@ -392,6 +393,7 @@ F: lib/librte_ethdev/rte_mtr*
>
> Baseband API - EXPERIMENTAL
> M: Nicolas Chautru <nicolas.chautru@intel.com>
> +R: Tom Rix <trix@redhat.com>
> T: git://dpdk.org/next/dpdk-next-crypto
> F: lib/librte_bbdev/
> F: doc/guides/prog_guide/bbdev.rst
> --
> 2.18.1
next prev parent reply other threads:[~2020-10-01 21:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-01 14:30 trix
2020-10-01 21:22 ` Chautru, Nicolas [this message]
2020-10-01 21:54 ` Thomas Monjalon
2020-10-02 14:59 ` Tom Rix
2020-10-02 15:41 ` Thomas Monjalon
2020-10-02 16:35 ` Tom Rix
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=BY5PR11MB445159A9135C8F09F0983FA3F8300@BY5PR11MB4451.namprd11.prod.outlook.com \
--to=nicolas.chautru@intel.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
--cc=trix@redhat.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).