From: Kalle Valo <kvalo@kernel.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Arend Van Spriel <arend.vanspriel@broadcom.com>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Arend van Spriel <aspriel@gmail.com>,
Franky Lin <franky.lin@broadcom.com>,
Hante Meuleman <hante.meuleman@broadcom.com>,
linux-wireless@vger.kernel.org,
brcm80211-dev-list.pdl@broadcom.com,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: MAINTAINERS: wifi: brcm80211: remove non-existing SHA-cyfmac-dev-list@infineon.com
Date: Tue, 19 Dec 2023 12:53:18 +0200 [thread overview]
Message-ID: <8734vysbtt.fsf@kernel.org> (raw)
In-Reply-To: <29c3122ca8e4d72c07942d09dca7a0fbd0138024.camel@sipsolutions.net> (Johannes Berg's message of "Tue, 19 Dec 2023 11:41:18 +0100")
Johannes Berg <johannes@sipsolutions.net> writes:
> On Tue, 2023-12-19 at 10:01 +0100, Arend Van Spriel wrote:
>> >
>> > > When sending an email to SHA-cyfmac-dev-list@infineon.com, the server
>> > > responds '550 #5.1.0 Address rejected.'
>>
>> Is the claim here true? In another thread I replied all including this list
>> and I am not getting a bounce message.
>
> I also got the bounce, FWIW. And Lukas is using gmail ... if you're not
> accepting mail from gmail I'm not sure you get to call it "email" in the
> 21st century, for (better or) worse...
And is Infineon even contributing anything to upstream? At least I don't
have recollection any recent activity, though happy to be proven wrong.
We shouldn't have dormant information in MAINTAINERS file.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2023-12-19 10:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 12:11 [PATCH] MAINTAINERS: remove non-existing SHA-cyfmac-dev-list@infineon.com Lukas Bulwahn
2023-12-19 4:12 ` MAINTAINERS: wifi: brcm80211: " Kalle Valo
2023-12-19 9:01 ` Arend Van Spriel
2023-12-19 10:37 ` Lukas Bulwahn
2023-12-19 10:41 ` Johannes Berg
2023-12-19 10:53 ` Kalle Valo [this message]
2023-12-20 11:22 ` Bagas Sanjaya
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=8734vysbtt.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=arend.vanspriel@broadcom.com \
--cc=aspriel@gmail.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=johannes@sipsolutions.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lukas.bulwahn@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox