public inbox for rust-for-linux@vger.kernel.org
 help / color / mirror / Atom feed
From: "Danilo Krummrich" <dakr@kernel.org>
To: "Timur Tabi" <ttabi@nvidia.com>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
	"Alice Ryhl" <aliceryhl@google.com>,
	"Gary Guo" <gary@garyguo.net>, <mmaurer@google.com>,
	"John Hubbard" <jhubbard@nvidia.com>,
	"Alexandre Courbot" <acourbot@nvidia.com>,
	"Joel Fernandes" <joelagnelf@nvidia.com>,
	"Eliot Courtney" <ecourtney@nvidia.com>,
	<rust-for-linux@vger.kernel.org>
Subject: Re: [PATCH v11 0/6] gpu: nova-core: expose the logging buffers via debugfs
Date: Wed, 25 Mar 2026 01:42:33 +0100	[thread overview]
Message-ID: <DHBG2PPAL2ED.3R4OC4W6XS54P@kernel.org> (raw)
In-Reply-To: <20260319212658.2541610-1-ttabi@nvidia.com>

On Thu Mar 19, 2026 at 10:26 PM CET, Timur Tabi wrote:

Applied to drm-rust-next, thanks!

> Timur Tabi (6):
>   rust: device: add device name method
>   rust: uaccess: add write_dma() for copying from DMA buffers to
>     userspace

    [ Rebase onto Coherent<T> changes; remove unnecessary turbofish from
      cast(). - Danilo ]

>   rust: dma: implement BinaryWriter for CoherentAllocation<u8>

    [ Rebase onto Coherent<T> changes. - Danilo ]

>   gpu: nova-core: Replace module_pci_driver! with explicit module init
>   gpu: nova-core: create debugfs root in module init
>   gpu: nova-core: create GSP-RM logging buffers debugfs entries

    [ Rebase onto Coherent<T> changes. - Danilo ]

There's a small follow-up series in [1].

[1] https://lore.kernel.org/driver-core/20260325003921.3420-1-dakr@kernel.org/

      parent reply	other threads:[~2026-03-25  0:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-19 21:26 [PATCH v11 0/6] gpu: nova-core: expose the logging buffers via debugfs Timur Tabi
2026-03-19 21:26 ` [PATCH v11 1/6] rust: device: add device name method Timur Tabi
2026-03-19 21:26 ` [PATCH v11 2/6] rust: uaccess: add write_dma() for copying from DMA buffers to userspace Timur Tabi
2026-03-24 20:00   ` Alice Ryhl
2026-03-19 21:26 ` [PATCH v11 3/6] rust: dma: implement BinaryWriter for CoherentAllocation<u8> Timur Tabi
2026-03-19 21:26 ` [PATCH v11 4/6] gpu: nova-core: Replace module_pci_driver! with explicit module init Timur Tabi
2026-03-19 21:26 ` [PATCH v11 5/6] gpu: nova-core: create debugfs root in " Timur Tabi
2026-03-19 21:26 ` [PATCH v11 6/6] gpu: nova-core: create GSP-RM logging buffers debugfs entries Timur Tabi
2026-03-25  0:42 ` Danilo Krummrich [this message]

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=DHBG2PPAL2ED.3R4OC4W6XS54P@kernel.org \
    --to=dakr@kernel.org \
    --cc=acourbot@nvidia.com \
    --cc=aliceryhl@google.com \
    --cc=ecourtney@nvidia.com \
    --cc=gary@garyguo.net \
    --cc=jhubbard@nvidia.com \
    --cc=joelagnelf@nvidia.com \
    --cc=mmaurer@google.com \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=ttabi@nvidia.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