From: Simon Horman <horms@kernel.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Networking <netdev@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Karsten Keil <isdn@linux-pingi.de>
Subject: Re: [PATCH net] MAINTAINERS: mark ISDN subsystem as orphan
Date: Mon, 27 Oct 2025 19:28:55 +0000 [thread overview]
Message-ID: <aP_H935zm6YwW997@horms.kernel.org> (raw)
In-Reply-To: <20251023092406.56699-1-bagasdotme@gmail.com>
On Thu, Oct 23, 2025 at 04:24:06PM +0700, Bagas Sanjaya wrote:
> We have not heard any activities from Karsten in years:
>
> - Last review tag was nine years ago in commit a921e9bd4e22a7
> ("isdn: i4l: move active-isdn drivers to staging")
> - Last message on lore was in October 2020 [1].
>
> Furthermore, messages to isdn mailing list bounce.
>
> Mark the subsystem as orphan to reflect these.
>
> [1]: https://lore.kernel.org/all/0ee243a9-9937-ad26-0684-44b18e772662@linux-pingi.de/
>
> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
> ---
> netdev maintainers: I have sent request message to Karsten off-list prior to
> sending this patch. Please hold off applying it until a week later when I
> will inform whether he responds or not.
FTR, I checked the information in the commit message,
and my searches match what is written above.
I agree waiting a week is a good plan.
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2025-10-27 19:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-23 9:24 [PATCH net] MAINTAINERS: mark ISDN subsystem as orphan Bagas Sanjaya
2025-10-27 19:28 ` Simon Horman [this message]
2025-10-28 7:13 ` Bagas Sanjaya
2025-10-28 1:00 ` 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=aP_H935zm6YwW997@horms.kernel.org \
--to=horms@kernel.org \
--cc=bagasdotme@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=isdn@linux-pingi.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox