All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Simon Horman <horms@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
	pabeni@redhat.com, Marcel Holtmann <marcel@holtmann.org>,
	Johan Hedberg <johan.hedberg@gmail.com>,
	Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
	linux-bluetooth@vger.kernel.org,
	Johan Hedberg <johan.hedberg@intel.com>
Subject: Re: [PATCH net 5/7] MAINTAINERS: Bluetooth: retire Johan (for now?)
Date: Thu, 11 Jan 2024 16:21:14 -0800	[thread overview]
Message-ID: <20240111162114.658a752b@kernel.org> (raw)
In-Reply-To: <20240110151309.GD9296@kernel.org>

On Wed, 10 Jan 2024 15:13:09 +0000 Simon Horman wrote:
> + Johan Hedberg <johan.hedberg@intel.com>
> 
> On Tue, Jan 09, 2024 at 08:45:15AM -0800, Jakub Kicinski wrote:
> > Johan moved to maintaining the Zephyr Bluetooth stack,
> > and we haven't heard from him on the ML in 3 years
> > (according to lore), and seen any tags in git in 4 years.
> > Trade the MAINTAINER entry for CREDITS, we can revert
> > whenever Johan comes back to Linux hacking :)
> > 
> > Subsystem BLUETOOTH SUBSYSTEM
> >   Changes 173 / 986 (17%)
> >   Last activity: 2023-12-22
> >   Marcel Holtmann <marcel@holtmann.org>:
> >     Author 91cb4c19118a 2022-01-27 00:00:00 52
> >     Committer edcb185fa9c4 2022-05-23 00:00:00 446
> >     Tags 000c2fa2c144 2023-04-23 00:00:00 523
> >   Johan Hedberg <johan.hedberg@gmail.com>:  
> 
> I'm not arguing that this change isn't appropriate.
> But, nit picking the description above,
> I do think there has been some git activity within
> the last 4 years, albeit from a different email address.
> 
> The most recent Bluetooth Drivers patch I found committed by Johan is:
> 
> commit 0671c0662383eefc272e107364cba7fe229dee44
> Author:     Hans de Goede <hdegoede@redhat.com>
> AuthorDate: Sat Dec 5 16:02:01 2020 +0100
> Commit:     Johan Hedberg <johan.hedberg@intel.com>
> CommitDate: Mon Dec 7 17:01:54 2020 +0200
> 
> For reference, the most recent patched that I could
> find authored by Johan for Bluetooth Drivers is:
> 
> commit 6c3711ec64fd23a9abc8aaf59a9429569a6282df
> Author:     Johan Hedberg <johan.hedberg@intel.com>
> AuthorDate: Sat Aug 4 23:40:26 2018 +0300
> Commit:     Marcel Holtmann <marcel@holtmann.org>
> CommitDate: Sat Aug 4 23:23:32 2018 +0200

Indeed, my grepping must have failed me :(
If someone pops up in the top three reviewers at the end of the report
it's fairly easy to catch that they use a different address, but that
wasn't the case here. In any case, here is the report after having
added the correct email alias -- just to confirm that the script itself
is not buggy :)

Subsystem BLUETOOTH SUBSYSTEM
  Changes 173 / 986 (17%)
  Last activity: 2023-12-22
  Marcel Holtmann <marcel@holtmann.org>:
    Author 91cb4c19118a 2022-01-27 00:00:00 52
    Committer edcb185fa9c4 2022-05-23 00:00:00 446
    Tags 000c2fa2c144 2023-04-23 00:00:00 523
  Johan Hedberg <johan.hedberg@gmail.com>:
    Committer e6ed8b78eae5 2020-12-07 00:00:00 60
    Tags e6ed8b78eae5 2020-12-07 00:00:00 69
  Luiz Augusto von Dentz <luiz.dentz@gmail.com>:
    Author d03376c18592 2023-12-22 00:00:00 241
    Committer da9065caa594 2023-12-22 00:00:00 341
    Tags da9065caa594 2023-12-22 00:00:00 493
  Top reviewers:
    [33]: alainm@chromium.org
    [31]: mcchou@chromium.org
    [27]: abhishekpandit@chromium.org


  reply	other threads:[~2024-01-12  0:21 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-09 16:45 [PATCH net 0/7] Networking MAINTAINERS spring 2024 cleanup Jakub Kicinski
2024-01-09 16:45 ` [PATCH net 1/7] MAINTAINERS: eth: mtk: move John to CREDITS Jakub Kicinski
2024-01-10 14:48   ` Simon Horman
2024-01-10 15:34     ` John Crispin
2024-01-10 15:46       ` Simon Horman
2024-01-09 16:45 ` [PATCH net 2/7] MAINTAINERS: eth: mt7530: move Landen Chao " Jakub Kicinski
2024-01-10  6:57   ` Arınç ÜNAL
2024-01-09 16:45 ` [PATCH net 3/7] MAINTAINERS: eth: mvneta: move Thomas " Jakub Kicinski
2024-01-09 16:55   ` Andrew Lunn
2024-01-09 17:43     ` Marcin Wojtas
2024-01-09 19:01       ` Andrew Lunn
2024-01-09 20:53         ` Marcin Wojtas
2024-01-10  7:49   ` Thomas Petazzoni
2024-01-09 16:45 ` [PATCH net 4/7] MAINTAINERS: eth: mark Cavium liquidio as an Orphan Jakub Kicinski
2024-01-09 21:36   ` Derek Chickles
2024-01-09 16:45 ` [PATCH net 5/7] MAINTAINERS: Bluetooth: retire Johan (for now?) Jakub Kicinski
2024-01-10 15:13   ` Simon Horman
2024-01-12  0:21     ` Jakub Kicinski [this message]
2024-02-02 21:22   ` patchwork-bot+bluetooth
2024-01-09 16:45 ` [PATCH net 6/7] MAINTAINERS: mark ax25 as Orphan Jakub Kicinski
2024-01-10 15:22   ` Simon Horman
2024-01-11  3:11     ` Eric Johnson
     [not found]       ` <CAG9xq4Efi9O4LbJj7kYjne1EjPJ9BkWiuNy_QxYTHW9eyGz5bg@mail.gmail.com>
2024-01-11  3:31         ` Michael
2024-01-11 11:39       ` Paolo Abeni
2024-01-11 15:45         ` Michael
2024-01-09 16:45 ` [PATCH net 7/7] MAINTAINERS: ibmvnic: drop Dany from reviewers Jakub Kicinski
2024-01-10 15:23   ` Simon Horman
2024-01-12  0:30 ` [PATCH net 0/7] Networking MAINTAINERS spring 2024 cleanup patchwork-bot+netdevbpf

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=20240111162114.658a752b@kernel.org \
    --to=kuba@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=johan.hedberg@gmail.com \
    --cc=johan.hedberg@intel.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@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 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.