mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Danilo Krummrich <dakr@kernel.org>
To: Matteo Kloiber <kernel@matt3o12.de>
Cc: dakr@kernel.org, acourbot@nvidia.com, aliceryhl@google.com,
	ojeda@kernel.org, airlied@gmail.com, simona@ffwll.ch,
	abdiel.janulgue@gmail.com, daniel.almeida@collabora.com,
	robin.murphy@arm.com, a.hindborg@kernel.org,
	nova-gpu@lists.linux.dev, dri-devel@lists.freedesktop.org,
	driver-core@lists.linux.dev, rust-for-linux@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: (subset) [PATCH v2 0/2] rust: honor the maximum DMA segment size
Date: Thu, 24 Sep 2026 17:51:27 +0200	[thread overview]
Message-ID: <20260924155127.96245-1-dakr@kernel.org> (raw)
In-Reply-To: <20260913210828.125655-1-kernel@matt3o12.de>

On Sun, 13 Sep 2026 23:08:26 +0200, Matteo Kloiber wrote:
> [PATCH v2 0/2] rust: honor the maximum DMA segment size

Applied, thanks!

  Branch: driver-core-testing
  Tree:   git://git.kernel.org/pub/scm/linux/kernel/git/driver-core/driver-core.git

[2/2] rust: scatterlist: honor the device's maximum segment size
      commit: c15c5befd6d6

The patch will appear in the next linux-next integration (typically within 24
hours on weekdays).

The patch is in the driver-core-testing branch and will be promoted to
driver-core-next after validation.

      parent reply	other threads:[~2026-09-24 15:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-13 21:08 Matteo Kloiber
2026-09-13 21:08 ` [PATCH v2 1/2] gpu: nova-core: declare unlimited DMA max " Matteo Kloiber
2026-09-21  3:44   ` Alexandre Courbot
2026-09-13 21:08 ` [PATCH v2 2/2] rust: scatterlist: honor the device's maximum " Matteo Kloiber
2026-09-24 15:51 ` 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=20260924155127.96245-1-dakr@kernel.org \
    --to=dakr@kernel.org \
    --cc=a.hindborg@kernel.org \
    --cc=abdiel.janulgue@gmail.com \
    --cc=acourbot@nvidia.com \
    --cc=airlied@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=daniel.almeida@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=driver-core@lists.linux.dev \
    --cc=kernel@matt3o12.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nova-gpu@lists.linux.dev \
    --cc=ojeda@kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=simona@ffwll.ch \
    /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

all inboxes | Powered by JetHome®