From: "Onur Özkan" <work@onurozkan.dev>
To: rust-for-linux@vger.kernel.org
Cc: ojeda@kernel.org, nathan@kernel.org, nicolas.schier@linux.dev,
masahiroy@kernel.org, aliceryhl@google.com,
thomas.weissschuh@linutronix.de, tamird@gmail.com,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
alex.gaynor@gmail.com, boqun.feng@gmail.com, gary@garyguo.net,
bjorn3_gh@protonmail.com, lossin@kernel.org,
a.hindborg@kernel.org, tmgross@umich.edu, dakr@kernel.org
Subject: Re: [PATCH v2 0/1] rust: add `rustcheck` make target for check-only builds
Date: Thu, 9 Oct 2025 15:54:57 +0300 [thread overview]
Message-ID: <20251009155457.22131e41@nimda.home> (raw)
In-Reply-To: <20250915115311.3025-1-work@onurozkan.dev>
On Mon, 15 Sep 2025 14:53:10 +0300
Onur Özkan <work@onurozkan.dev> wrote:
> Changes in v2:
> - Couple of indentation fixes in rust/Makefile.
>
> Onur Özkan (1):
> rust: add `rustcheck` make target for check-only builds
>
> Makefile | 7 +++++
> rust/Makefile | 73
> +++++++++++++++++++++++++++++++++++++++++++++++++++ 2 files changed,
> 80 insertions(+)
>
A friendly ping on this patch. It's been over two weeks with no
feedback, would appreciate any thoughts or suggestions.
Regards,
Onur
prev parent reply other threads:[~2025-10-09 12:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-15 11:53 [PATCH v2 0/1] rust: add `rustcheck` make target for check-only builds Onur Özkan
2025-09-15 11:53 ` [PATCH v2 1/1] " Onur Özkan
2025-09-22 6:02 ` Nicolas Schier
2025-09-23 3:47 ` Onur Özkan
2025-10-10 18:56 ` Nicolas Schier
2025-09-16 12:06 ` [PATCH v2 0/1] " Onur
2025-10-09 12:54 ` Onur Özkan [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=20251009155457.22131e41@nimda.home \
--to=work@onurozkan.dev \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=nicolas.schier@linux.dev \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tamird@gmail.com \
--cc=thomas.weissschuh@linutronix.de \
--cc=tmgross@umich.edu \
/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).