All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
	pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
	corbet@lwn.net, skhan@linuxfoundation.org, marcel@holtmann.org,
	luiz.dentz@gmail.com, mchehab+huawei@kernel.org,
	jani.nikula@intel.com, gregkh@linuxfoundation.org,
	demarchi@kernel.org, rdunlap@infradead.org,
	justonli@chromium.org, ivecera@redhat.com,
	jonathan.cameron@huawei.com, kees@kernel.org,
	marco.crivellari@suse.com, ferr.lambarginio@gmail.com,
	nihaal@cse.iitm.ac.in, mingo@kernel.org, tglx@kernel.org,
	linmq006@gmail.com, linux-doc@vger.kernel.org,
	linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH net-deletions] net: remove ISDN subsystem and Bluetooth CMTP
Date: Thu, 30 Apr 2026 17:55:44 +0000	[thread overview]
Message-ID: <177757174432.3109994.10971496392017658764.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260421022108.1299678-1-kuba@kernel.org>

Hello:

This patch was applied to bluetooth/bluetooth-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:

On Mon, 20 Apr 2026 19:21:07 -0700 you wrote:
> Remove the ISDN (mISDN, CAPI) subsystem and Bluetooth CMTP protocol
> from the kernel tree.
> 
> ISDN is a pretty old technology and it's unclear whether anyone still
> uses it. I went over the last few years of git history and all the
> commits are either tree-wide conversions or syzbot/static analyzer
> fixes.
> 
> [...]

Here is the summary with links:
  - [net-deletions] net: remove ISDN subsystem and Bluetooth CMTP
    https://git.kernel.org/bluetooth/bluetooth-next/c/4f10f1dfb235

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-04-30 17:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-21  2:21 [PATCH net-deletions] net: remove ISDN subsystem and Bluetooth CMTP Jakub Kicinski
2026-04-21  4:18 ` [net-deletions] " bluez.test.bot
2026-04-21  6:03 ` [PATCH net-deletions] " Greg KH
2026-04-21 13:47 ` Stephen Hemminger
2026-04-21 13:55 ` Luiz Augusto von Dentz
2026-04-21 17:12   ` Randy Dunlap
2026-04-22 10:55 ` Simon Horman
2026-04-27  0:37 ` patchwork-bot+netdevbpf
2026-04-30 17:55 ` patchwork-bot+bluetooth [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=177757174432.3109994.10971496392017658764.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=demarchi@kernel.org \
    --cc=edumazet@google.com \
    --cc=ferr.lambarginio@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=horms@kernel.org \
    --cc=ivecera@redhat.com \
    --cc=jani.nikula@intel.com \
    --cc=jonathan.cameron@huawei.com \
    --cc=justonli@chromium.org \
    --cc=kees@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linmq006@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=marco.crivellari@suse.com \
    --cc=mchehab+huawei@kernel.org \
    --cc=mingo@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nihaal@cse.iitm.ac.in \
    --cc=pabeni@redhat.com \
    --cc=rdunlap@infradead.org \
    --cc=skhan@linuxfoundation.org \
    --cc=tglx@kernel.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.