From: Wolfram Sang <wsa@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: Florian Fainelli <f.fainelli@gmail.com>,
Greg KH <gregkh@linuxfoundation.org>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
linux-mips@vger.kernel.org
Subject: [RFC PATCH 0/2] vlynq: remove bus support
Date: Sat, 16 Sep 2023 11:11:22 +0200 [thread overview]
Message-ID: <20230916091125.3221-1-wsa@kernel.org> (raw)
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
I'd like to clean up the 'drivers' directory and Kconfig menu, at least
a little. One major thing I noticed is that VLYNQ can actually be
removed. From patch 2:
---
There are no users with a vlynq_driver in the Kernel tree. So, remove
the bus driver which hardly has seen any activity since 2009. It was
even marked EXPERIMENTAL as long as that symbol existed. OpenWRT had
some out-of-tree drivers which they probably intended to upport, but AR7
devices are not supported anymore because they are "stuck with Kernel
3.18" [1]. So, this code can go nowadays.
[1] https://openwrt.org/docs/techref/targets/ar7
---
Patch 1 removes MIPS specific bus initialization code which is the only
user of the VLYNQ bus currently.
Sending out as RFC to gather comments. Patches are based on 6.6-rc1 and
created with "--irreversible-delete" to save some space. They are
compile tested only, buildbots were happy.
I think this mainly goes to Florian Fainelli. Florian, what do you
think?
All the best!
Wolfram
Wolfram Sang (2):
MIPS: AR7: remove VLYNQ init
vlynq: remove bus driver
MAINTAINERS | 7 -
arch/mips/Kconfig | 1 -
arch/mips/ar7/platform.c | 193 +------
arch/mips/include/asm/mach-ar7/ar7.h | 1 -
drivers/Kconfig | 2 -
drivers/Makefile | 1 -
drivers/vlynq/Kconfig | 21 -
drivers/vlynq/Makefile | 6 -
drivers/vlynq/vlynq.c | 799 ---------------------------
include/linux/vlynq.h | 149 -----
10 files changed, 1 insertion(+), 1179 deletions(-)
delete mode 100644 drivers/vlynq/Kconfig
delete mode 100644 drivers/vlynq/Makefile
delete mode 100644 drivers/vlynq/vlynq.c
delete mode 100644 include/linux/vlynq.h
--
2.35.1
next reply other threads:[~2023-09-16 9:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-16 9:11 Wolfram Sang [this message]
2023-09-16 9:11 ` [RFC PATCH 1/2] MIPS: AR7: remove VLYNQ init Wolfram Sang
2023-09-16 11:11 ` [RFC PATCH 0/2] vlynq: remove bus support Jonas Gorski
2023-09-16 16:42 ` Florian Fainelli
2023-09-16 17:02 ` Wolfram Sang
2023-09-18 13:18 ` Wolfram Sang
2023-09-18 18:33 ` Florian Fainelli
2023-09-19 6:37 ` Wolfram Sang
2023-09-16 11:43 ` Greg KH
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=20230916091125.3221-1-wsa@kernel.org \
--to=wsa@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.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;
as well as URLs for NNTP newsgroup(s).