diff options
| author | Jakub Kicinski <kuba@kernel.org> | 2022-04-05 21:16:27 -0700 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2022-04-08 12:06:11 +0100 |
| commit | e05afd0848f8452edb7b4138536fae2aaf01552a (patch) | |
| tree | 7ffe959848d1f8f53332a3ab5213ae9e482f6e33 /drivers/atm/Makefile | |
| parent | 6e8805de30011959a4b3ffaa6614e3662ba4adce (diff) | |
| download | linux-rpi-e05afd0848f8452edb7b4138536fae2aaf01552a.tar.gz linux-rpi-e05afd0848f8452edb7b4138536fae2aaf01552a.tar.bz2 linux-rpi-e05afd0848f8452edb7b4138536fae2aaf01552a.zip | |
net: atm: remove the ambassador driver
The driver for ATM Ambassador devices 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.
In fact it sounds like the FW loading was broken from 2008
'til 2012 - see commit fcdc90b025e6 ("atm: forever loop loading
ambassador firmware").
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>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/atm/Makefile')
| -rw-r--r-- | drivers/atm/Makefile | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/drivers/atm/Makefile b/drivers/atm/Makefile index aa191616a72e..99ecbc280643 100644 --- a/drivers/atm/Makefile +++ b/drivers/atm/Makefile @@ -7,7 +7,6 @@ fore_200e-y := fore200e.o obj-$(CONFIG_ATM_ZATM) += zatm.o uPD98402.o obj-$(CONFIG_ATM_NICSTAR) += nicstar.o -obj-$(CONFIG_ATM_AMBASSADOR) += ambassador.o obj-$(CONFIG_ATM_HORIZON) += horizon.o obj-$(CONFIG_ATM_IA) += iphase.o suni.o obj-$(CONFIG_ATM_FORE200E) += fore_200e.o |