From: Geert Stappers <stappers@stappers.nl>
To: rust-for-linux@vger.kernel.org
Subject: Re: [PATCH v4 00/20] Rust support, nn/nn
Date: Sun, 13 Feb 2022 10:31:35 +0100 [thread overview]
Message-ID: <20220213093135.7hvlvbsawcu2bjzg@gpm.stappers.nl> (raw)
In-Reply-To: <20220212130410.6901-1-ojeda@kernel.org>
On Sat, Feb 12, 2022 at 02:03:26PM +0100, Miguel Ojeda wrote:
> Rust support
>
> This is the patch series (v4) to add support for Rust as a second
> language to the Linux kernel.
> ...
Where is patch 20/20?
Long:
I'm missing patch 20/20. With the v3 series I did mis patch 21/21.
In other projects I see,
patches 01/nn up to nn/nn and cover letter 00/nn.
At https://www.spinics.net/lists/linux-serial/ you find
[PATCH v2 0/2] serial: 8250: Correct basic issues with the PCI blacklist, Maciej W. Rozycki
` [PATCH v2 2/2] serial: 8250: Report which option to enable for blacklisted PCI devices, Maciej W. Rozycki
` [PATCH v2 1/2] serial: 8250: Correct Kconfig help text for blacklisted PCI devices, Maciej W. Rozycki
[PATCH v3 0/2] serial: 8250: Fixes for Oxford Semiconductor 950 UARTs, Maciej W. Rozycki
` [PATCH v3 1/2] serial: 8250: Fold EndRun device support into OxSemi Tornado code, Maciej W. Rozycki
` [PATCH v3 2/2] serial: 8250: Add proper clock handling for OxSemi PCIe devices, Maciej W. Rozycki
[PATCH 0/2] serial: 8250: Correct basic issues with the PCI blacklist, Maciej W. Rozycki
` [PATCH 1/2] serial: 8250: Correct Kconfig help text for blacklisted PCI devices, Maciej W. Rozycki
` [PATCH 2/2] serial: 8250: Report which option to enable for blacklisted PCI devices, Maciej W. Rozycki
[PATCH v8 0/6] serial: mvebu-uart: Support for higher baudrates, Marek Behún
` [PATCH v8 1/6] math64: New DIV_U64_ROUND_CLOSEST helper, Marek Behún
` [PATCH v8 2/6] dt-bindings: mvebu-uart: document DT bindings for marvell,armada-3700-uart-clock, Marek Behún
` [PATCH v8 3/6] serial: mvebu-uart: implement UART clock driver for configuring UART base clock, Marek Behún
` [PATCH v8 4/6] dt-bindings: mvebu-uart: update information about UART clock, Marek Behún
` [PATCH v8 5/6] arm64: dts: marvell: armada-37xx: add device node for UART clock and use it, Marek Behún
` [PATCH v8 6/6] serial: mvebu-uart: implement support for baudrates higher than 230400 Bd, Marek Behún
At https://lore.kernel.org/rust-for-linux/ you find
[PATCH v4 00/20] Rust support
` [PATCH v4 01/20] kallsyms: support "big" kernel symbols
` [PATCH v4 02/20] kallsyms: increase maximum kernel symbol length to 512
` [PATCH v4 03/20] kallsyms: use the correct buffer size for symbols
` [PATCH v4 04/20] rust: add C helpers
` [PATCH v4 05/20] rust: add `compiler_builtins` crate
` [PATCH v4 07/20] rust: add `build_error` crate
` [PATCH v4 08/20] rust: add `macros` crate
` [PATCH v4 09/20] rust: add `kernel` crate's `sync` module
` [PATCH v4 11/20] rust: export generated symbols
` [PATCH v4 12/20] vsprintf: add new `%pA` format specifier
` [PATCH v4 13/20] scripts: add `generate_rust_analyzer.py`
` [PATCH v4 14/20] scripts: decode_stacktrace: demangle Rust symbols
` [PATCH v4 16/20] Kbuild: add Rust support
` [PATCH v4 17/20] samples: add Rust examples
` [PATCH v4 18/20] MAINTAINERS: Rust
` [PATCH v4 19/20] [RFC] drivers: gpio: PrimeCell PL061 in Rust
Hench my question: Where is patch 20/20?
Groeten
Geert Stappers
--
Silence is hard to parse
next prev parent reply other threads:[~2022-02-13 9:41 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-12 13:03 [PATCH v4 00/20] Rust support Miguel Ojeda
2022-02-12 13:03 ` [PATCH v4 01/20] kallsyms: support "big" kernel symbols Miguel Ojeda
2022-02-12 13:03 ` [PATCH v4 02/20] kallsyms: increase maximum kernel symbol length to 512 Miguel Ojeda
2022-02-22 8:19 ` Petr Mladek
2022-02-22 12:45 ` Miguel Ojeda
2022-02-12 13:03 ` [PATCH v4 03/20] kallsyms: use the correct buffer size for symbols Miguel Ojeda
2022-02-12 13:03 ` [PATCH v4 04/20] rust: add C helpers Miguel Ojeda
2022-02-12 13:03 ` [PATCH v4 05/20] rust: add `compiler_builtins` crate Miguel Ojeda
2022-02-12 13:03 ` [PATCH v4 07/20] rust: add `build_error` crate Miguel Ojeda
2022-02-12 13:03 ` [PATCH v4 08/20] rust: add `macros` crate Miguel Ojeda
2022-02-12 13:03 ` [PATCH v4 09/20] rust: add `kernel` crate's `sync` module Miguel Ojeda
2022-02-12 13:03 ` [PATCH v4 11/20] rust: export generated symbols Miguel Ojeda
2022-02-12 13:03 ` [PATCH v4 12/20] vsprintf: add new `%pA` format specifier Miguel Ojeda
2022-02-14 10:18 ` Andy Shevchenko
2022-02-14 10:52 ` Rasmus Villemoes
2022-02-14 11:36 ` David Laight
2022-02-14 14:04 ` Miguel Ojeda
2022-02-14 12:12 ` Miguel Ojeda
2022-02-22 9:29 ` Petr Mladek
2022-02-22 10:35 ` Rasmus Villemoes
2022-02-24 9:55 ` Petr Mladek
2022-02-14 12:27 ` Miguel Ojeda
2022-02-14 13:54 ` Andy Shevchenko
2022-02-14 14:56 ` Miguel Ojeda
2022-02-12 13:03 ` [PATCH v4 13/20] scripts: add `generate_rust_analyzer.py` Miguel Ojeda
2022-02-12 13:03 ` [PATCH v4 14/20] scripts: decode_stacktrace: demangle Rust symbols Miguel Ojeda
2022-02-12 13:03 ` [PATCH v4 16/20] Kbuild: add Rust support Miguel Ojeda
2022-02-12 14:16 ` Russell King (Oracle)
2022-02-12 15:47 ` Miguel Ojeda
2022-02-12 16:18 ` Russell King (Oracle)
2022-02-12 18:32 ` Miguel Ojeda
2022-02-12 18:27 ` John Paul Adrian Glaubitz
2022-02-12 18:57 ` Miguel Ojeda
2022-02-12 13:03 ` [PATCH v4 17/20] samples: add Rust examples Miguel Ojeda
2022-02-12 13:03 ` [PATCH v4 18/20] MAINTAINERS: Rust Miguel Ojeda
2022-02-12 13:03 ` [PATCH v4 19/20] [RFC] drivers: gpio: PrimeCell PL061 in Rust Miguel Ojeda
2022-02-13 9:31 ` Geert Stappers [this message]
2022-02-13 9:55 ` [PATCH v4 00/20] Rust support, nn/nn Greg KH
2022-02-13 10:52 ` Geert Stappers
2022-02-14 14:16 ` Miguel Ojeda
2022-02-14 14:48 ` Geert Stappers
[not found] ` <20220212130410.6901-11-ojeda@kernel.org>
2022-02-14 5:27 ` [PATCH v4 10/20] rust: add `kernel` crate Sergey Senozhatsky
2022-02-14 13:36 ` Miguel Ojeda
2022-02-22 9:06 ` Petr Mladek
2022-02-22 12:48 ` Miguel Ojeda
2022-02-24 12:39 ` Petr Mladek
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=20220213093135.7hvlvbsawcu2bjzg@gpm.stappers.nl \
--to=stappers@stappers.nl \
--cc=rust-for-linux@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).