All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Networking <netdev@vger.kernel.org>,
	Linux Kernel Janitors <kernel-janitors@vger.kernel.org>,
	Kees Cook <keescook@chromium.org>,
	Jakub Kicinski <kuba@kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	"Jiri Slaby (SUSE)" <jirislaby@kernel.org>,
	Justin Stitt <justinstitt@google.com>,
	Kunwu Chan <chentao@kylinos.cn>,
	Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
	Nathan Chancellor <nathan@kernel.org>,
	"Steven Rostedt (Google)" <rostedt@goodmis.org>,
	Karsten Keil <isdn@linux-pingi.de>,
	Karsten Keil <keil@b1-systems.de>,
	YouHong Li <liyouhong@kylinos.cn>
Subject: Re: [PATCH net 0/2] ISDN/mISDN maintenanceship cleanup
Date: Thu, 21 Dec 2023 17:52:16 +0700	[thread overview]
Message-ID: <ZYQY4OW4U28OY-i0@archie.me> (raw)
In-Reply-To: <2023122121-yiddish-unproven-d793@gregkh>

[-- Attachment #1: Type: text/plain, Size: 931 bytes --]

On Thu, Dec 21, 2023 at 10:32:58AM +0100, Greg Kroah-Hartman wrote:
> On Thu, Dec 21, 2023 at 04:17:37PM +0700, Bagas Sanjaya wrote:
> > On 12/21/23 16:14, Bagas Sanjaya wrote:
> > > When I'm looking at simple typofix against ISDN subsystem [1], I find
> > > out more about subsystem activity. It turns out that the subsystem
> > > maintainer has been inactive since 3 years ago. And also, when I test
> > > sending "Lorem ipsum" message to the subsystem mailing list, it gets
> > > bounced.
> > > 
> > 
> > Oops, sorry not adding the link.
> > 
> > [1]: https://lore.kernel.org/lkml/20231221024758.1317603-1-liyouhong@kylinos.cn/
> 
> I too like to ignore pointless changes like this at times.  Just because
> others do, does NOT mean that the subsystem is not being maintained.

Unless maintainers in question agree after their inactivity.

Ciao!

-- 
An old man doll... just what I always wanted! - Clara

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      reply	other threads:[~2023-12-21 10:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-21  9:14 [PATCH net 0/2] ISDN/mISDN maintenanceship cleanup Bagas Sanjaya
2023-12-21  9:14 ` [PATCH net 1/2] MAINTAINERS: Remove Karsten Keil Bagas Sanjaya
2023-12-21  9:32   ` Greg Kroah-Hartman
2023-12-21 10:49     ` Bagas Sanjaya
2023-12-21 10:54       ` Greg Kroah-Hartman
2023-12-21 11:23         ` Bagas Sanjaya
2023-12-21 11:53           ` Greg Kroah-Hartman
2023-12-21 14:06             ` Bagas Sanjaya
2023-12-21  9:14 ` [PATCH net 2/2] MAINTAINERS: Remove isdn4linux@listserv.isdn4linux.de mailing list Bagas Sanjaya
2023-12-21  9:17 ` [PATCH net 0/2] ISDN/mISDN maintenanceship cleanup Bagas Sanjaya
2023-12-21  9:32   ` Greg Kroah-Hartman
2023-12-21 10:52     ` Bagas Sanjaya [this message]

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=ZYQY4OW4U28OY-i0@archie.me \
    --to=bagasdotme@gmail.com \
    --cc=chentao@kylinos.cn \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=davem@davemloft.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=isdn@linux-pingi.de \
    --cc=jirislaby@kernel.org \
    --cc=justinstitt@google.com \
    --cc=keescook@chromium.org \
    --cc=keil@b1-systems.de \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liyouhong@kylinos.cn \
    --cc=nathan@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    /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.