From: Jon Mason <jdmason@kudzu.us>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, ntb@lists.linux.dev
Subject: [GIT PULL] NTB bug fixes for 6.18
Date: Fri, 10 Oct 2025 08:26:42 -0400 [thread overview]
Message-ID: <aOj7glAc85SXWodE@athena.kudzu.us> (raw)
Hello Linus,
Here are a few NTB bug fixes and minor updates for 6.18. The patches
have been in my tree for some time, but the tag is new.
Please consider pulling them.
Thanks,
Jon
The following changes since commit 8f5ae30d69d7543eee0d70083daf4de8fe15d585:
Linux 6.17-rc1 (2025-08-10 19:41:16 +0300)
are available in the Git repository at:
https://github.com/jonmason/ntb tags/ntb-6.18
for you to fetch changes up to 006824a1cb3bd4001745a2b1cc83c43fad522851:
NTB: epf: Add Renesas rcar support (2025-09-22 09:35:21 -0400)
----------------------------------------------------------------
Add support for Renesas R-Car and allow arbitrary BAR mapping in EPF. Update
ntb_hw_amd to support the latest generation secondary topology and add a
new maintainer. Fix a bug by adding a mutex to ensure `link_event_callback`
executes sequentially.
----------------------------------------------------------------
Basavaraj Natikar (2):
ntb_hw_amd: Update amd_ntb_get_link_status to support latest generation secondary topology
MAINTAINERS: Update for the NTB AMD driver maintainer
Jerome Brunet (2):
NTB: epf: Allow arbitrary BAR mapping
NTB: epf: Add Renesas rcar support
fuyuanli (1):
ntb: Add mutex to make link_event_callback executed linearly.
MAINTAINERS | 1 +
drivers/ntb/hw/amd/ntb_hw_amd.c | 18 +++++-
drivers/ntb/hw/amd/ntb_hw_amd.h | 1 +
drivers/ntb/hw/epf/ntb_hw_epf.c | 118 +++++++++++++++++++++++-----------------
drivers/ntb/ntb_transport.c | 7 +++
5 files changed, 94 insertions(+), 51 deletions(-)
next reply other threads:[~2025-10-10 12:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-10 12:26 Jon Mason [this message]
2025-10-10 18:26 ` [GIT PULL] NTB bug fixes for 6.18 pr-tracker-bot
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=aOj7glAc85SXWodE@athena.kudzu.us \
--to=jdmason@kudzu.us \
--cc=linux-kernel@vger.kernel.org \
--cc=ntb@lists.linux.dev \
--cc=torvalds@linux-foundation.org \
/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