From: Greg KH <gregkh@linuxfoundation.org>
To: Wolfram Sang <wsa@kernel.org>
Cc: linux-kernel@vger.kernel.org,
Florian Fainelli <f.fainelli@gmail.com>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
linux-mips@vger.kernel.org
Subject: Re: [RFC PATCH 0/2] vlynq: remove bus support
Date: Sat, 16 Sep 2023 13:43:33 +0200 [thread overview]
Message-ID: <2023091624-outthink-griminess-11cd@gregkh> (raw)
In-Reply-To: <20230916091125.3221-1-wsa@kernel.org>
On Sat, Sep 16, 2023 at 11:11:22AM +0200, Wolfram Sang wrote:
> 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?
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
prev parent reply other threads:[~2023-09-16 11:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-16 9:11 [RFC PATCH 0/2] vlynq: remove bus support Wolfram Sang
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 [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=2023091624-outthink-griminess-11cd@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.com \
--cc=wsa@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 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).