Linux CXL
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-rdma@vger.kernel.org, linux-cxl@vger.kernel.org,
	linux-kernel@vger.kernel.org, Dave Jiang <dave.jiang@intel.com>,
	Saeed Mahameed <saeedm@nvidia.com>
Subject: [GIT PULL] Please pull FWCTL subsystem changes
Date: Tue, 18 Aug 2026 21:11:12 -0300	[thread overview]
Message-ID: <20260819001112.GA200468@nvidia.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1933 bytes --]

Hi Linus,

Interesting update this time, we have a rust binding for fwctl in this
PR that is expected to be used with the Nova GPU driver next
cycle.

There is a compile failure merge conflict that needs this
one liner in the merge commit:

 https://lore.kernel.org/r/20260818105350.361218-1-ojeda@kernel.org

Thanks,
Jason

The following changes since commit 075b74841bd0065a3bda3440873c747938e69b68:

  Linux 7.2-rc6 (2026-08-02 16:24:24 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/fwctl/fwctl.git tags/for-linus-fwctl

for you to fetch changes up to e052daab94ee8c4081c91de3549772bd1c235729:

  rust: introduce abstractions for fwctl (2026-08-14 19:21:17 -0300)

----------------------------------------------------------------
fwctl 7.3 pull request

- Support more commands in bnxt, this completes what they originally
  wanted to do

- Rust bindings for fwctl. The Nova GPU is expected to use them next cycle

----------------------------------------------------------------
Pavan Chebbi (2):
      bnxt_en: Update bnxt firmware spec
      fwctl/bnxt: Add DMA buffer support for HWRM commands

Zhi Wang (1):
      rust: introduce abstractions for fwctl

 MAINTAINERS                     |   3 +
 drivers/fwctl/Kconfig           |  12 +
 drivers/fwctl/bnxt/main.c       | 396 ++++++++++++++++++++++++++-
 include/linux/bnxt/hsi.h        | 585 +++++++++++++++++++++++++++++++++++++++
 include/uapi/fwctl/bnxt.h       |   4 +
 rust/bindings/bindings_helper.h |   1 +
 rust/helpers/fwctl.c            |  17 ++
 rust/helpers/helpers.c          |   3 +-
 rust/kernel/fwctl.rs            | 593 ++++++++++++++++++++++++++++++++++++++++
 rust/kernel/lib.rs              |   2 +
 10 files changed, 1610 insertions(+), 6 deletions(-)
 create mode 100644 rust/helpers/fwctl.c
 create mode 100644 rust/kernel/fwctl.rs

-- 
Jason

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

             reply	other threads:[~2026-08-19  0:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-19  0:11 Jason Gunthorpe [this message]
2026-08-19 19:53 ` [GIT PULL] Please pull FWCTL subsystem changes pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2026-05-22 23:25 Jason Gunthorpe
2026-05-23 16:23 ` pr-tracker-bot
2026-04-16 14:11 Jason Gunthorpe
2026-04-17  4:28 ` pr-tracker-bot
2025-10-01 19:35 Jason Gunthorpe
2025-10-04  1:41 ` pr-tracker-bot
2025-04-17 12:36 Jason Gunthorpe
2025-04-17 18:57 ` pr-tracker-bot
2025-03-24 15:13 [GIT PULL] Please pull fwctl " Jason Gunthorpe
2025-03-26 17:13 ` Jakub Kicinski
2025-03-29 18:24 ` 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=20260819001112.GA200468@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=dave.jiang@intel.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=saeedm@nvidia.com \
    --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