All of lore.kernel.org
 help / color / mirror / Atom feed
From: Moritz Fischer <mdf@kernel.org>
To: gregkh@linuxfoundation.org
Cc: linux-fpga@vger.kernel.org, yilun.xu@intel.com, hao.wu@intel.com,
	moritzf@google.com
Subject: [GIT PULL] FPGA Manager changes for 5.19-rc1
Date: Sun, 15 May 2022 14:48:34 -0700	[thread overview]
Message-ID: <YoF1Mo1ZK69orQ0I@archbook> (raw)

The following changes since commit 3123109284176b1532874591f7c81f3837bbdc17:

  Linux 5.18-rc1 (2022-04-03 14:08:21 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/fpga/linux-fpga tags/fpga-for-5.19-rc1

for you to fetch changes up to ae23f746d7442909a19bd43397b567145d6e5db3:

  fpga: dfl: Allow Port to be linked to FME's DFL (2022-05-10 16:05:38 +0800)

----------------------------------------------------------------
FPGA Manager changes for 5.19-rc1

FPGA Manager

- My change moves the linux-fpga repository to a shared
  location w/ shared responsibilities between maintainers
- Nava's changes fix coding style and kernel-docs

DFL

- Matthew's change allows ports to be linked to FMEs.
- Tianfei's changes clean up some documentation and
  ensure the feature type is checked before parsing IRQs

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

Signed-off-by: Moritz Fischer <mdf@kernel.org>

----------------------------------------------------------------
Matthew Gerlach (1):
      fpga: dfl: Allow Port to be linked to FME's DFL

Moritz Fischer (1):
      MAINTAINERS: Update linux-fpga repository location

Nava kishore Manne (4):
      fpga: fix for coding style issues
      fpga: fpga-mgr: fix kernel-doc warnings
      fpga: Use tab instead of space indentation
      fpga: fpga-region: fix kernel-doc formatting issues

Tianfei zhang (2):
      fpga: dfl: check feature type before parse irq info
      Documentation: fpga: dfl: add link address of feature id table

 Documentation/fpga/dfl.rst       |  5 +++++
 MAINTAINERS                      |  2 +-
 drivers/fpga/Makefile            |  6 +++---
 drivers/fpga/dfl-pci.c           |  9 +++++++++
 drivers/fpga/dfl.c               | 38 ++++++++++++++++++++++----------------
 drivers/fpga/dfl.h               |  1 +
 drivers/fpga/fpga-mgr.c          | 13 +++++++++----
 drivers/fpga/fpga-region.c       |  6 +++---
 drivers/fpga/of-fpga-region.c    | 22 ++++++++++++----------
 include/linux/fpga/fpga-region.h |  6 +++---
 10 files changed, 68 insertions(+), 40 deletions(-)

                 reply	other threads:[~2022-05-15 21:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=YoF1Mo1ZK69orQ0I@archbook \
    --to=mdf@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hao.wu@intel.com \
    --cc=linux-fpga@vger.kernel.org \
    --cc=moritzf@google.com \
    --cc=yilun.xu@intel.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 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.