All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@amd.com>
To: <u-boot@lists.denx.de>, <git@xilinx.com>, <p.bruenn@beckhoff.com>
Cc: Alexander Dahl <ada@thorsis.com>,
	Alexander Graf <agraf@csgraf.de>,
	Dmitry Rokosov <ddrokosov@salutedevices.com>,
	Heinrich Schuchardt <xypron.glpk@gmx.de>,
	Ilias Apalodimas <ilias.apalodimas@linaro.org>,
	Mattijs Korpershoek <mkorpershoek@kernel.org>,
	Muhammad Hazim Izzat Zamri
	<muhammad.hazim.izzat.zamri@altera.com>,
	Pieter Van Trappen <pieter.van.trappen@cern.ch>,
	Simon Glass <sjg@chromium.org>,
	Svyatoslav Ryhel <clamor95@gmail.com>,
	Tom Rini <trini@konsulko.com>
Subject: [PATCH 0/3] fpga: Remove lattice and ACEX1 support
Date: Fri, 25 Jul 2025 13:25:51 +0200	[thread overview]
Message-ID: <cover.1753442748.git.michal.simek@amd.com> (raw)

Hi,

when fpga drivers were enabled via sandbox some coverity issues came and
make no sense to fix them when there is no user of these drivers that's why
it is easier just remove them completely.

Another candidate for removal is FPGA_CYCLON2 which is enabled only by
mx53cx9020_defconfig.
Patrick: Is this board still maintained?

Thanks,
Michal


Michal Simek (3):
  fpga: xilinx: Check valid desc structure
  fpga: Remove ancient ACEX1K support
  fpga: lattice: Remove unused support

 configs/sandbox_defconfig |    2 -
 drivers/fpga/ACEX1K.c     |  245 ---
 drivers/fpga/Kconfig      |   12 -
 drivers/fpga/Makefile     |    2 -
 drivers/fpga/altera.c     |    5 +-
 drivers/fpga/fpga.c       |   23 -
 drivers/fpga/ivm_core.c   | 3149 -------------------------------------
 drivers/fpga/lattice.c    |  379 -----
 drivers/fpga/xilinx.c     |    3 +
 include/ACEX1K.h          |   49 -
 include/fpga.h            |    1 -
 include/lattice.h         |  298 ----
 12 files changed, 4 insertions(+), 4164 deletions(-)
 delete mode 100644 drivers/fpga/ACEX1K.c
 delete mode 100644 drivers/fpga/ivm_core.c
 delete mode 100644 drivers/fpga/lattice.c
 delete mode 100644 include/lattice.h

-- 
2.43.0

base-commit: 021783860f7e628f7c4e0c101707cd4250e6d61f
branch: debian-sent3

             reply	other threads:[~2025-07-25 11:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-25 11:25 Michal Simek [this message]
2025-07-25 11:25 ` [PATCH 1/3] fpga: xilinx: Check valid desc structure Michal Simek
2025-07-25 11:25 ` [PATCH 2/3] fpga: Remove ancient ACEX1K support Michal Simek
2025-07-25 12:10   ` Alexander Dahl
2025-07-25 12:17     ` Michal Simek
2025-07-25 12:30       ` Alexander Dahl
2025-07-25 11:25 ` [PATCH 3/3] fpga: lattice: Remove unused support Michal Simek
2025-07-25 12:00 ` [PATCH 0/3] fpga: Remove lattice and ACEX1 support Alexander Dahl
2025-07-25 12:03   ` Michal Simek
2025-07-25 14:00     ` Tom Rini
2025-07-25 14:42       ` Alexander Dahl
2025-07-25 13:55 ` Tom Rini
2025-07-26  5:38 ` Patrick Brünn

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=cover.1753442748.git.michal.simek@amd.com \
    --to=michal.simek@amd.com \
    --cc=ada@thorsis.com \
    --cc=agraf@csgraf.de \
    --cc=clamor95@gmail.com \
    --cc=ddrokosov@salutedevices.com \
    --cc=git@xilinx.com \
    --cc=ilias.apalodimas@linaro.org \
    --cc=mkorpershoek@kernel.org \
    --cc=muhammad.hazim.izzat.zamri@altera.com \
    --cc=p.bruenn@beckhoff.com \
    --cc=pieter.van.trappen@cern.ch \
    --cc=sjg@chromium.org \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --cc=xypron.glpk@gmx.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.