All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Shannon Nelson <shannon.nelson@amd.com>
Cc: netdev@vger.kernel.org, netdev-driver-reviewers@vger.kernel.org
Subject: Re: [ANN] netdev development stats for 6.4
Date: Mon, 1 May 2023 14:21:55 -0700	[thread overview]
Message-ID: <20230501142155.6b84a188@kernel.org> (raw)
In-Reply-To: <667f3a20-aaa3-edd6-8769-7096649c5737@amd.com>

On Fri, 28 Apr 2023 15:08:27 -0700 Shannon Nelson wrote:
> > On the "bad" side the only constants are   
> 
> Can you give a little more description of what is being measured in this 
> section - is this reviews versus submissions?  And what are some ways 
> for a company to get out of the wrong list?

As Andrew explained the way to get off the "negative" list is 
to comment on other peoples patches :)

> > Histograms!
> > -----------
> > 
> > I was wondering about the distribution of "tenure" in the community.
> > Are we relying on "old timers" to review the code? Are the "old timers"
> > still coding? Do we have any new participants at all?  
> 
> Is this relying on the .mailmap for finding longevity?  I probably need 
> to add a couple more entries here.

I was matching on name or email. Hopefully name would be good enough 
to catch most cases.

  parent reply	other threads:[~2023-05-01 21:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-28 20:57 [ANN] netdev development stats for 6.4 Jakub Kicinski
2023-04-28 22:08 ` Shannon Nelson
2023-04-28 22:51   ` Andrew Lunn
2023-05-01 21:21   ` Jakub Kicinski [this message]
2023-05-03  8:01 ` Leon Romanovsky
2023-05-03 14:47   ` Jakub Kicinski

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=20230501142155.6b84a188@kernel.org \
    --to=kuba@kernel.org \
    --cc=netdev-driver-reviewers@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=shannon.nelson@amd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.