Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Mark Brown <broonie@debian.org>
To: Tamir Duberstein <tamird@gmail.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
	"Viresh Kumar" <viresh.kumar@linaro.org>,
	"Miguel Ojeda" <ojeda@kernel.org>,
	"Alex Gaynor" <alex.gaynor@gmail.com>,
	"Boqun Feng" <boqun.feng@gmail.com>,
	"Gary Guo" <gary@garyguo.net>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"Benno Lossin" <lossin@kernel.org>,
	"Andreas Hindborg" <a.hindborg@kernel.org>,
	"Alice Ryhl" <aliceryhl@google.com>,
	"Trevor Gross" <tmgross@umich.edu>,
	"Danilo Krummrich" <dakr@kernel.org>,
	"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
	"Maxime Ripard" <mripard@kernel.org>,
	"Thomas Zimmermann" <tzimmermann@suse.de>,
	"David Airlie" <airlied@gmail.com>,
	"Simona Vetter" <simona@ffwll.ch>,
	"FUJITA Tomonori" <fujita.tomonori@gmail.com>,
	"Andrew Lunn" <andrew@lunn.ch>,
	"Heiner Kallweit" <hkallweit1@gmail.com>,
	"Russell King" <linux@armlinux.org.uk>,
	"David S. Miller" <davem@davemloft.net>,
	"Eric Dumazet" <edumazet@google.com>,
	"Jakub Kicinski" <kuba@kernel.org>,
	"Paolo Abeni" <pabeni@redhat.com>,
	"Michael Turquette" <mturquette@baylibre.com>,
	"Stephen Boyd" <sboyd@kernel.org>,
	"Breno Leitao" <leitao@debian.org>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Luis Chamberlain" <mcgrof@kernel.org>,
	"Russ Weight" <russ.weight@linux.dev>,
	"Dave Ertman" <david.m.ertman@intel.com>,
	"Ira Weiny" <ira.weiny@intel.com>,
	"Leon Romanovsky" <leon@kernel.org>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
	"Arnd Bergmann" <arnd@arndb.de>,
	"Brendan Higgins" <brendan.higgins@linux.dev>,
	"David Gow" <davidgow@google.com>, "Rae Moar" <rmoar@google.com>,
	"Jens Axboe" <axboe@kernel.dk>,
	"Alexandre Courbot" <acourbot@nvidia.com>,
	"Alexander Viro" <viro@zeniv.linux.org.uk>,
	"Christian Brauner" <brauner@kernel.org>,
	"Jan Kara" <jack@suse.cz>, "Liam Girdwood" <lgirdwood@gmail.com>,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
	rust-for-linux@vger.kernel.org, nouveau@lists.freedesktop.org,
	dri-devel@lists.freedesktop.org, netdev@vger.kernel.org,
	linux-clk@vger.kernel.org, linux-pci@vger.kernel.org,
	linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com,
	linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v2 00/19] rust: replace `kernel::c_str!` with C-Strings
Date: Thu, 25 Sep 2025 15:01:11 +0100	[thread overview]
Message-ID: <111409f1-33cd-4cd1-b3fd-e38402a82c9f@sirena.org.uk> (raw)
In-Reply-To: <20250925-core-cstr-cstrings-v2-0-78e0aaace1cd@gmail.com>

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

On Thu, Sep 25, 2025 at 09:53:48AM -0400, Tamir Duberstein wrote:
> This series depends on step 3[0].
> 
> Subsystem maintainers: I would appreciate your `Acked-by`s so that this
> can be taken through Miguel's tree (where the previous series must go).

Given that we're almost at the merge window isn't it likely that these
will get applied once the current rust tree is in mainline?

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

  parent reply	other threads:[~2025-09-25 14:01 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-25 13:53 [PATCH v2 00/19] rust: replace `kernel::c_str!` with C-Strings Tamir Duberstein
2025-09-25 13:53 ` [PATCH v2 01/19] drivers: net: " Tamir Duberstein
2025-09-25 13:53 ` [PATCH v2 02/19] gpu: nova-core: " Tamir Duberstein
2025-09-25 13:53 ` [PATCH v2 03/19] rust: auxiliary: " Tamir Duberstein
2025-09-25 13:53 ` [PATCH v2 04/19] rust: clk: " Tamir Duberstein
2025-09-25 13:53 ` [PATCH v2 05/19] rust: configfs: " Tamir Duberstein
2025-09-25 13:53 ` [PATCH v2 06/19] rust: cpufreq: " Tamir Duberstein
2025-09-25 13:53 ` [PATCH v2 07/19] rust: device: " Tamir Duberstein
2025-09-25 13:53 ` [PATCH v2 08/19] rust: firmware: " Tamir Duberstein
2025-09-25 13:53 ` [PATCH v2 09/19] rust: kunit: " Tamir Duberstein
2025-09-25 13:53 ` [PATCH v2 10/19] rust: macros: " Tamir Duberstein
2025-09-25 13:53 ` [PATCH v2 11/19] rust: miscdevice: " Tamir Duberstein
2025-09-25 13:54 ` [PATCH v2 12/19] rust: net: " Tamir Duberstein
2025-09-25 13:54 ` [PATCH v2 13/19] rust: pci: " Tamir Duberstein
2025-09-25 13:54 ` [PATCH v2 14/19] rust: platform: " Tamir Duberstein
2025-09-25 13:54 ` [PATCH v2 15/19] rust: seq_file: " Tamir Duberstein
2025-09-25 13:54 ` [PATCH v2 16/19] rust: str: " Tamir Duberstein
2025-09-25 13:54 ` [PATCH v2 17/19] rust: sync: " Tamir Duberstein
2025-10-16 10:42   ` Andreas Hindborg
2025-09-25 13:54 ` [PATCH v2 18/19] rust: io: " Tamir Duberstein
2025-09-25 22:12   ` Benno Lossin
2025-09-25 22:25   ` Danilo Krummrich
2025-10-01  9:28   ` Alice Ryhl
2025-09-25 13:54 ` [PATCH v2 19/19] rust: regulator: " Tamir Duberstein
2025-09-25 22:12   ` Benno Lossin
2025-10-01  9:29   ` Alice Ryhl
2025-10-15  9:48   ` Mark Brown
2025-09-25 14:01 ` Mark Brown [this message]
2025-09-26 18:46   ` [PATCH v2 00/19] rust: " Miguel Ojeda
2025-09-29 19:57 ` Miguel Ojeda
2025-12-22 20:04 ` (subset) " Mark Brown
  -- strict thread matches above, loose matches on Subject: below --
2025-08-13 15:59 Tamir Duberstein
2025-08-13 20:11 ` Mark Brown
2025-08-14  8:24   ` Alice Ryhl
2025-08-14  9:07     ` Miguel Ojeda

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=111409f1-33cd-4cd1-b3fd-e38402a82c9f@sirena.org.uk \
    --to=broonie@debian.org \
    --cc=a.hindborg@kernel.org \
    --cc=acourbot@nvidia.com \
    --cc=airlied@gmail.com \
    --cc=alex.gaynor@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=andrew@lunn.ch \
    --cc=arnd@arndb.de \
    --cc=axboe@kernel.dk \
    --cc=bhelgaas@google.com \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=brauner@kernel.org \
    --cc=brendan.higgins@linux.dev \
    --cc=dakr@kernel.org \
    --cc=davem@davemloft.net \
    --cc=david.m.ertman@intel.com \
    --cc=davidgow@google.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=edumazet@google.com \
    --cc=fujita.tomonori@gmail.com \
    --cc=gary@garyguo.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=hkallweit1@gmail.com \
    --cc=ira.weiny@intel.com \
    --cc=jack@suse.cz \
    --cc=kuba@kernel.org \
    --cc=kunit-dev@googlegroups.com \
    --cc=kwilczynski@kernel.org \
    --cc=leitao@debian.org \
    --cc=leon@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=lossin@kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mcgrof@kernel.org \
    --cc=mripard@kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=netdev@vger.kernel.org \
    --cc=nouveau@lists.freedesktop.org \
    --cc=ojeda@kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rafael@kernel.org \
    --cc=rmoar@google.com \
    --cc=russ.weight@linux.dev \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=sboyd@kernel.org \
    --cc=simona@ffwll.ch \
    --cc=tamird@gmail.com \
    --cc=tmgross@umich.edu \
    --cc=tzimmermann@suse.de \
    --cc=viresh.kumar@linaro.org \
    --cc=viro@zeniv.linux.org.uk \
    /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