From: patchwork-bot+bluetooth@kernel.org
To: Ethan Nelson-Moore <enelsonmoore@gmail.com>
Cc: linux-mips@vger.kernel.org, linux-bluetooth@vger.kernel.org,
linux@armlinux.org.uk, chenhuacai@kernel.org, kernel@xen0n.name,
tsbogend@alpha.franken.de, maddy@linux.ibm.com,
mpe@ellerman.id.au, npiggin@gmail.com, chleroy@kernel.org,
marcel@holtmann.org, luiz.dentz@gmail.com, ebiggers@kernel.org,
ardb@kernel.org, herbert@gondor.apana.org.au, tytso@mit.edu,
andre.draszik@linaro.org, geert@linux-m68k.org, kuba@kernel.org,
horms@kernel.org, johan.korsnes@gmail.com, david@ixit.cz
Subject: Re: [PATCH bluetooth-next v2] bluetooth: remove all PCMCIA drivers
Date: Mon, 04 May 2026 17:10:06 +0000 [thread overview]
Message-ID: <177791460656.801187.2564297588269230821.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260503033201.19719-1-enelsonmoore@gmail.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Sat, 2 May 2026 20:31:21 -0700 you wrote:
> PCMCIA is almost completely obsolete (the last computers supporting it
> natively were from ~2009), and the general consensus [1] seems to be
> that support for it should be gradually removed from the kernel.
>
> In 2023, an initial step of removing all the PCMCIA char drivers was
> taken in commit 9b12f050c76f ("char: pcmcia: remove all the drivers"),
> and that has not been reverted, so it seems logical to continue this
> process by removing more low-hanging fruit.
>
> [...]
Here is the summary with links:
- [bluetooth-next,v2] bluetooth: remove all PCMCIA drivers
https://git.kernel.org/bluetooth/bluetooth-next/c/88cb3906d295
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-05-04 17:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-03 3:31 [PATCH bluetooth-next v2] bluetooth: remove all PCMCIA drivers Ethan Nelson-Moore
2026-05-03 5:30 ` [bluetooth-next,v2] " bluez.test.bot
2026-05-04 17:10 ` 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=177791460656.801187.2564297588269230821.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=andre.draszik@linaro.org \
--cc=ardb@kernel.org \
--cc=chenhuacai@kernel.org \
--cc=chleroy@kernel.org \
--cc=david@ixit.cz \
--cc=ebiggers@kernel.org \
--cc=enelsonmoore@gmail.com \
--cc=geert@linux-m68k.org \
--cc=herbert@gondor.apana.org.au \
--cc=horms@kernel.org \
--cc=johan.korsnes@gmail.com \
--cc=kernel@xen0n.name \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=luiz.dentz@gmail.com \
--cc=maddy@linux.ibm.com \
--cc=marcel@holtmann.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=tsbogend@alpha.franken.de \
--cc=tytso@mit.edu \
/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.