Hey Tom, 
Thanks for your recent reviews.
My only concern with this is how in reality you would be able to serve the role 
of maintainer for these drivers/lib/test and engage in meaningful discussions? 
Do you understand 3GPP and the related processing and what these devices are 
actually doing? Supporting them in linux and generic coding guide line review 
is one thing, but maintainer would need broader understanding arguably. 
I think you reviews are super valuable (dpdk coding guide lines, error 
handling...) and I can make sure to include you generally for review for all 
related contributions, I am just unsure whether in reality that corresponds to 
what would be required to be a maintainer. 
I am just thinking aloud here, let me know what you think
Thanks
Nic

> -----Original Message-----
> From: t...@redhat.com <t...@redhat.com>
> Sent: Monday, October 5, 2020 8:00 AM
> To: tho...@monjalon.net; Chautru, Nicolas <nicolas.chau...@intel.com>
> Cc: dev@dpdk.org; Tom Rix <t...@redhat.com>
> Subject: [PATCH] maintainers: add self to baseband maintainers
> 
> From: Tom Rix <t...@redhat.com>
> 
> 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 <t...@redhat.com>
> ---
>  MAINTAINERS | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index c0abbe0fc..22e80580a 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -18,7 +18,6 @@ Descriptions of section entries:
>       K: Keyword regex pattern to match content.
>          One regex pattern per line. Multiple K: lines acceptable.
> 
> -
>  General Project Administration
>  ------------------------------
> 
> @@ -392,6 +391,7 @@ F: lib/librte_ethdev/rte_mtr*
> 
>  Baseband API - EXPERIMENTAL
>  M: Nicolas Chautru <nicolas.chau...@intel.com>
> +M: Tom Rix <t...@redhat.com>
>  T: git://dpdk.org/next/dpdk-next-crypto
>  F: lib/librte_bbdev/
>  F: doc/guides/prog_guide/bbdev.rst
> --
> 2.18.1

Reply via email to