All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: "Alexis Lothoré" <alexis.lothore@bootlin.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	 Ajay Singh <ajay.kathat@microchip.com>,
	 Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	 linux-wireless@vger.kernel.org,
	 Igor Mitsyanko <imitsyanko@quantenna.com>,
	 Sergey Matyukevich <geomatsi@gmail.com>,
	 kernel test robot <lkp@intel.com>,
	 Claudiu Beznea <claudiu.beznea@tuxon.dev>,
	 srini.raju@purelifi.com
Subject: Re: wireless: orphan qfnfmac and plfxlc drivers?
Date: Thu, 15 Feb 2024 19:21:32 +0200	[thread overview]
Message-ID: <871q9dej8j.fsf@kernel.org> (raw)
In-Reply-To: <875xypejwt.fsf_-_@kernel.org> (Kalle Valo's message of "Thu, 15 Feb 2024 19:06:58 +0200")

Kalle Valo <kvalo@kernel.org> writes:

> (changing subject)
>
> Alexis Lothoré <alexis.lothore@bootlin.com> writes:
>
>> Also, my mail provider returns error 550 (No Such User Here) for quantenna
>> driver maintainer (<imitsyanko@quantenna.com>, taken from MAINTAINERS). I've
>> seen no recent activity from him on the ML, is he still around ?
>
> I found a bounce for imitsyanko@quantenna.com from 2022 so I guess it's
> time to orphan qtnfmac?
>
> Also the purelife maintainer Srini Raju (CCed) is bouncing, that's
> another candidate to orphan.

And confirmed, I just got bounces for both of these maintainers. Patches
welcome to orphan these drivers.

<srini.raju@purelifi.com>: host
    purelifi-com.mail.protection.outlook.com[52.101.68.16] said: 550 5.4.1
    Recipient address rejected: Access denied.
    [DB5PEPF00014B8D.eurprd02.prod.outlook.com 2024-02-15T17:07:03.735Z
    08DC2C530F4F7910] (in reply to RCPT TO command)

<imitsyanko@quantenna.com>: host mail.quantenna.com[50.87.249.29] said: 550 No
    Such User Here (in reply to RCPT TO command)

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

  reply	other threads:[~2024-02-15 17:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-15 14:13 [PATCH 0/2] wifi: nl80211/wilc1000: force WLAN_AKM_SUITE_SAE to big endian in NL80211_CMD_EXTERNAL_AUTH Alexis Lothoré
2024-02-15 14:13 ` [PATCH 1/2] wifi: nl80211: force WLAN_AKM_SUITE_SAE in " Alexis Lothoré
2024-02-15 16:58   ` Kalle Valo
2024-02-16  8:21     ` Alexis Lothoré
2024-02-16  9:34       ` Kalle Valo
2024-02-15 14:13 ` [PATCH 2/2] wifi: wilc1000: remove AKM suite be32 conversion for external auth request Alexis Lothoré
2024-02-21 18:54   ` Kalle Valo
2024-02-15 15:50 ` [PATCH 0/2] wifi: nl80211/wilc1000: force WLAN_AKM_SUITE_SAE to big endian in NL80211_CMD_EXTERNAL_AUTH Alexis Lothoré
2024-02-15 17:06   ` wireless: orphan qfnfmac and plfxlc drivers? Kalle Valo
2024-02-15 17:21     ` Kalle Valo [this message]
2024-02-15 18:51       ` Jeff Johnson
2024-02-16  9:37         ` Kalle Valo
2024-02-26  2:13           ` Igor Mitsyanko
2024-02-27 14:00             ` Kalle Valo
2024-02-28  3:02               ` Stefan Lippers-Hollmann

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=871q9dej8j.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=ajay.kathat@microchip.com \
    --cc=alexis.lothore@bootlin.com \
    --cc=claudiu.beznea@tuxon.dev \
    --cc=geomatsi@gmail.com \
    --cc=imitsyanko@quantenna.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=srini.raju@purelifi.com \
    --cc=thomas.petazzoni@bootlin.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.