From: Arnd Bergmann <arnd@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: "David Miller" <davem@davemloft.net>,
pabeni@redhat.com, Networking <netdev@vger.kernel.org>,
"Krzysztof Hałasa" <khalasa@piap.pl>,
"Andrew Stanley-Jones" <asj@cban.com>,
"Rob Braun" <bbraun@vix.com>, "Michael Graff" <explorer@vix.com>,
"Matt Thomas" <matt@3am-software.com>,
"Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
"open list:BROADCOM NVRAM DRIVER" <linux-mips@vger.kernel.org>,
"Linus Walleij" <linus.walleij@linaro.org>
Subject: Re: [PATCH net-next] net: wan: remove the lanmedia (lmc) driver
Date: Wed, 6 Apr 2022 09:48:32 +0200 [thread overview]
Message-ID: <CAK8P3a0N=Rn95T1jZCCcOcF4WiBsMkObw4FLjbZd91wbAi2zww@mail.gmail.com> (raw)
In-Reply-To: <20220406041548.643503-1-kuba@kernel.org>
On Wed, Apr 6, 2022 at 6:15 AM Jakub Kicinski <kuba@kernel.org> wrote:
>
> The driver for LAN Media WAN interfaces spews build warnings on
> microblaze. The virt_to_bus() calls discard the volatile keyword.
> The right thing to do would be to migrate this driver to a modern
> DMA API but it seems unlikely anyone is actually using it.
> There had been no fixes or functional changes here since
> the git era begun.
>
> Let's remove this driver, there isn't much changing in the APIs,
> if users come forward we can apologize and revert.
>
> Link: https://lore.kernel.org/all/20220321144013.440d7fc0@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com/
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Acked-by: Arnd Bergmann <arnd@arndb.de>
next prev parent reply other threads:[~2022-04-06 12:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 4:15 [PATCH net-next] net: wan: remove the lanmedia (lmc) driver Jakub Kicinski
2022-04-06 7:48 ` Arnd Bergmann [this message]
2022-04-06 11:11 ` Thomas Bogendoerfer
2022-04-06 11:46 ` Krzysztof Hałasa
2022-04-06 14:30 ` patchwork-bot+netdevbpf
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='CAK8P3a0N=Rn95T1jZCCcOcF4WiBsMkObw4FLjbZd91wbAi2zww@mail.gmail.com' \
--to=arnd@kernel.org \
--cc=asj@cban.com \
--cc=bbraun@vix.com \
--cc=davem@davemloft.net \
--cc=explorer@vix.com \
--cc=khalasa@piap.pl \
--cc=kuba@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-mips@vger.kernel.org \
--cc=matt@3am-software.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tsbogend@alpha.franken.de \
/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.