DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: "trix@redhat.com" <trix@redhat.com>,
	"Chautru, Nicolas" <nicolas.chautru@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] maintainers: New Reviewer entry type added to MAINTAINERS
Date: Thu, 01 Oct 2020 23:54:08 +0200	[thread overview]
Message-ID: <3460938.iZNE5J4TDP@thomas> (raw)
In-Reply-To: <BY5PR11MB445159A9135C8F09F0983FA3F8300@BY5PR11MB4451.namprd11.prod.outlook.com>

01/10/2020 23:22, Chautru, Nicolas:
> From: trix@redhat.com <trix@redhat.com>
> > 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>
> 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>
> >  Baseband API - EXPERIMENTAL
> >  M: Nicolas Chautru <nicolas.chautru@intel.com>
> > +R: Tom Rix <trix@redhat.com>

I don't understand the need of differenciating maintainer and reviewer.
If you are trusted enough, why not just being co-maintainer?

  reply	other threads:[~2020-10-01 21:54 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
2020-10-01 21:54   ` Thomas Monjalon [this message]
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3460938.iZNE5J4TDP@thomas \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=nicolas.chautru@intel.com \
    --cc=trix@redhat.com \


* 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).