archive mirror
 help / color / mirror / Atom feed
From: Moritz Fischer <>
Subject: [GIT PULL] FPGA Manager changes for 5.15-rc1
Date: Wed, 4 Aug 2021 08:31:54 -0700	[thread overview]
Message-ID: <YQqy6mso7Ukf6NYq@archbook> (raw)

The following changes since commit 630211a17055bafd21fb83ae8c0002b2e214ebb2:

  fpga: fpga-mgr: wrap the write_sg() op (2021-07-24 15:10:31 -0700)

are available in the Git repository at:

  git:// tags/fpga-for-5.15

for you to fetch changes up to 4f45f3404960109843eaa92c8a4a850d6bdd9981:

  spi: spi-altera-dfl: support n5010 feature revision (2021-07-29 13:02:28 -0700)

FPGA Manager changes for 5.15-rc1

FPGA Manager

- Colin's change is a simple spelling cleanup.


- Martin's fist change exposes DFL feature revision to client drivers
- Martin's second change modifies a SPI driver to populate different
  spi_board_info modaliases based on the DFL feature revision

All patches have been reviewed on the mailing list, and have been in the
last few linux-next releases (as part of my for-next branch) without issues.

Signed-off-by: Moritz Fischer <>

Colin Ian King (1):
      fpga: Fix spelling mistake "eXchnage" -> "exchange" in Kconfig

Martin Hundebøll (2):
      fpga: dfl: expose feature revision from struct dfl_device
      spi: spi-altera-dfl: support n5010 feature revision

 drivers/fpga/Kconfig         |  2 +-
 drivers/fpga/dfl.c           | 27 +++++++++++++++++----------
 drivers/fpga/dfl.h           |  1 +
 drivers/spi/spi-altera-dfl.c | 21 ++++++++++++---------
 include/linux/dfl.h          |  1 +
 5 files changed, 32 insertions(+), 20 deletions(-)

             reply	other threads:[~2021-08-04 15:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-04 15:31 Moritz Fischer [this message]
2021-08-05 12:26 ` [GIT PULL] FPGA Manager changes for 5.15-rc1 Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2021-07-26  2:55 Moritz Fischer
2021-07-26  3:00 ` Moritz Fischer
2021-07-27 14:39   ` Greg KH
2021-07-27 16:13     ` Moritz Fischer
2021-07-27 16:45       ` Greg KH
2021-07-26  2:53 Moritz Fischer

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YQqy6mso7Ukf6NYq@archbook \ \ \ \ \

* 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).