Linux-FPGA Archive mirror
 help / color / mirror / Atom feed
From: Xu Yilun <yilun.xu@linux.intel.com>
To: gregkh@linuxfoundation.org
Cc: yilun.xu@linux.intel.com, yilun.xu@intel.com,
	linux-fpga@vger.kernel.org, hao.wu@intel.com, mdf@kernel.org
Subject: [GIT PULL] FPGA Manager changes for 6.9-rc1
Date: Thu, 29 Feb 2024 10:36:45 +0800	[thread overview]
Message-ID: <Zd/tvYnZg31SJLKz@yilunxu-OptiPlex-7050> (raw)

The following changes since commit 6613476e225e090cc9aad49be7fa504e290dd33d:

  Linux 6.8-rc1 (2024-01-21 14:11:32 -0800)

are available in the Git repository at:

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

for you to fetch changes up to b1a91ca25f15b6d7b311de4465854a5981dee3d3:

  fpga: remove redundant checks for bridge ops (2024-02-18 18:07:06 +0800)

----------------------------------------------------------------
FPGA Manager changes for 6.9-rc1

DFL:

- Ricardo's change makes dfl_bus_type const.

FPGA MGR core:

- Marco's change removes redundant checks for bridge ops.

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: Xu Yilun <yilun.xu@intel.com>

----------------------------------------------------------------
Marco Pagani (1):
      fpga: remove redundant checks for bridge ops

Ricardo B. Marliere (1):
      fpga: dfl: make dfl_bus_type const

 drivers/fpga/dfl.c         | 2 +-
 drivers/fpga/fpga-bridge.c | 8 ++++----
 2 files changed, 5 insertions(+), 5 deletions(-)

             reply	other threads:[~2024-02-29  2:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-29  2:36 Xu Yilun [this message]
2024-03-02 19:01 ` [GIT PULL] FPGA Manager changes for 6.9-rc1 Greg KH

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=Zd/tvYnZg31SJLKz@yilunxu-OptiPlex-7050 \
    --to=yilun.xu@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hao.wu@intel.com \
    --cc=linux-fpga@vger.kernel.org \
    --cc=mdf@kernel.org \
    --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 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 read-only IMAP folder(s) and NNTP newsgroup(s).