linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, pabeni@redhat.com, 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>,
	"Arnd Bergmann" <arnd@kernel.org>,
	linux-mips@vger.kernel.org, linus.walleij@linaro.org
Subject: Re: [PATCH net-next] net: wan: remove the lanmedia (lmc) driver
Date: Wed, 6 Apr 2022 13:11:01 +0200	[thread overview]
Message-ID: <20220406111101.GA19718@alpha.franken.de> (raw)
In-Reply-To: <20220406041548.643503-1-kuba@kernel.org>

On Tue, Apr 05, 2022 at 09:15:48PM -0700, Jakub Kicinski 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>
> ---
> CC: Krzysztof Hałasa <khalasa@piap.pl>
> CC: Andrew Stanley-Jones <asj@cban.com>
> CC: Rob Braun <bbraun@vix.com>
> CC: Michael Graff <explorer@vix.com>,
> CC: Matt Thomas <matt@3am-software.com>
> CC: Arnd Bergmann <arnd@kernel.org>
> CC: tsbogend@alpha.franken.de # MIPS
> CC: linux-mips@vger.kernel.org
> CC: linus.walleij@linaro.org
> ---
>  arch/mips/configs/gpr_defconfig  |    1 -
>  arch/mips/configs/mtx1_defconfig |    1 -
>  drivers/net/wan/Kconfig          |   28 -
>  drivers/net/wan/Makefile         |    2 -
>  drivers/net/wan/lmc/Makefile     |   18 -
>  drivers/net/wan/lmc/lmc.h        |   33 -
>  drivers/net/wan/lmc/lmc_debug.c  |   65 -
>  drivers/net/wan/lmc/lmc_debug.h  |   52 -
>  drivers/net/wan/lmc/lmc_ioctl.h  |  255 ----
>  drivers/net/wan/lmc/lmc_main.c   | 2009 ------------------------------
>  drivers/net/wan/lmc/lmc_media.c  | 1206 ------------------
>  drivers/net/wan/lmc/lmc_proto.c  |  106 --
>  drivers/net/wan/lmc/lmc_proto.h  |   18 -
>  drivers/net/wan/lmc/lmc_var.h    |  468 -------
>  14 files changed, 4262 deletions(-)
>  delete mode 100644 drivers/net/wan/lmc/Makefile
>  delete mode 100644 drivers/net/wan/lmc/lmc.h
>  delete mode 100644 drivers/net/wan/lmc/lmc_debug.c
>  delete mode 100644 drivers/net/wan/lmc/lmc_debug.h
>  delete mode 100644 drivers/net/wan/lmc/lmc_ioctl.h
>  delete mode 100644 drivers/net/wan/lmc/lmc_main.c
>  delete mode 100644 drivers/net/wan/lmc/lmc_media.c
>  delete mode 100644 drivers/net/wan/lmc/lmc_proto.c
>  delete mode 100644 drivers/net/wan/lmc/lmc_proto.h
>  delete mode 100644 drivers/net/wan/lmc/lmc_var.h

Acked-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

  parent reply	other threads:[~2022-04-06 13:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220406041548.643503-1-kuba@kernel.org>
2022-04-06  7:48 ` [PATCH net-next] net: wan: remove the lanmedia (lmc) driver Arnd Bergmann
2022-04-06 11:11 ` Thomas Bogendoerfer [this message]
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=20220406111101.GA19718@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=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 \
    /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).