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, mdf@kernel.org
Subject: [GIT PULL] FPGA Manager changes for 6.16-rc1
Date: Mon, 12 May 2025 00:26:55 +0800 [thread overview]
Message-ID: <aCDPz42LmQ47ANDX@yilunxu-OptiPlex-7050> (raw)
The following changes since commit 0af2f6be1b4281385b618cb86ad946eded089ac8:
Linux 6.15-rc1 (2025-04-06 13:11:33 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/fpga/linux-fpga tags/fpga-for-6.16-rc1
for you to fetch changes up to 6ebf1982038af12f3588417e4fd0417d2551da28:
fpga: fix potential null pointer deref in fpga_mgr_test_img_load_sgt() (2025-05-06 00:37:00 +0800)
----------------------------------------------------------------
FPGA Manager changes for 6.16-rc1
- Peter hands over the maintain role of m10bmc-sec driver to Matthew.
- Qasim's change fix potential NULL pointer for fpga test.
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>
----------------------------------------------------------------
Peter Colberg (1):
fpga: m10bmc-sec: change contact for secure update driver
Qasim Ijaz (1):
fpga: fix potential null pointer deref in fpga_mgr_test_img_load_sgt()
Documentation/ABI/testing/sysfs-driver-intel-m10-bmc | 4 ++--
.../ABI/testing/sysfs-driver-intel-m10-bmc-sec-update | 14 +++++++-------
MAINTAINERS | 2 +-
drivers/fpga/tests/fpga-mgr-test.c | 1 +
4 files changed, 11 insertions(+), 10 deletions(-)
next reply other threads:[~2025-05-11 16:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-11 16:26 Xu Yilun [this message]
2025-05-21 12:10 ` [GIT PULL] FPGA Manager changes for 6.16-rc1 Greg KH
2025-05-22 3:35 ` Xu Yilun
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=aCDPz42LmQ47ANDX@yilunxu-OptiPlex-7050 \
--to=yilun.xu@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--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 NNTP newsgroup(s).