public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Benno Lossin" <lossin@kernel.org>
To: "Tamir Duberstein" <tamird@kernel.org>,
	"Miguel Ojeda" <ojeda@kernel.org>,
	"Boqun Feng" <boqun.feng@gmail.com>,
	"Gary Guo" <gary@garyguo.net>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"Andreas Hindborg" <a.hindborg@kernel.org>,
	"Alice Ryhl" <aliceryhl@google.com>,
	"Trevor Gross" <tmgross@umich.edu>,
	"Danilo Krummrich" <dakr@kernel.org>,
	"Jesung Yang" <y.j3ms.n@gmail.com>
Cc: <rust-for-linux@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	"Nathan Chancellor" <nathan@kernel.org>,
	"Nicolas Schier" <nsc@kernel.org>,
	"Linux Kbuild mailing list" <linux-kbuild@vger.kernel.org>
Subject: Re: [PATCH v2 0/2] rust: reduce duplicate information
Date: Tue, 20 Jan 2026 20:27:19 +0100	[thread overview]
Message-ID: <DFTNX1DYBXWJ.24E4YYMAJSH9N@kernel.org> (raw)
In-Reply-To: <20260120-rust-analyzer-pin-init-duplication-v2-0-a1c76f0d3bef@kernel.org>

On Tue Jan 20, 2026 at 5:10 PM CET, Tamir Duberstein wrote:
> This series reuses `rust/Makefile`'s knowledge of `pin_init` and
> `pin_init_internal`'s `cfg`s in `scripts/generate_rust_analzyer.py` and
> reduces the ceremony needed to use that knowledge in the script.

This is a cool idea, I don't maintain the makefile code, so this doesn't
mean much, but it's on my radar :)

Acked-by: Benno Lossin <lossin@kernel.org>

Cheers,
Benno

> Signed-off-by: Tamir Duberstein <tamird@kernel.org>
> ---
> Changes in v2:
> - Split into two patches. (Miguel Ojeda)
> - CC kbuild. (Miguel Ojeda)
> - Link to v1: https://patch.msgid.link/20260116-rust-analyzer-pin-init-duplication-v1-1-5e85c5824a02@kernel.org
>
> ---
> Tamir Duberstein (2):
>       rust: kbuild: extract configs for reuse
>       scripts: generate_rust_analyzer.py: reduce cfg plumbing
>
>  rust/Makefile                     | 32 +++++++++++++++++++++++---------
>  scripts/generate_rust_analyzer.py | 13 +++++--------
>  2 files changed, 28 insertions(+), 17 deletions(-)
> ---
> base-commit: 24d479d26b25bce5faea3ddd9fa8f3a6c3129ea7
> change-id: 20260116-rust-analyzer-pin-init-duplication-a22d05221771
>
> Best regards,
> --  
> Tamir Duberstein <tamird@kernel.org>


      parent reply	other threads:[~2026-01-20 19:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-20 16:10 [PATCH v2 0/2] rust: reduce duplicate information Tamir Duberstein
2026-01-20 16:10 ` [PATCH v2 1/2] rust: kbuild: extract configs for reuse Tamir Duberstein
2026-01-26  4:15   ` Miguel Ojeda
2026-01-20 16:10 ` [PATCH v2 2/2] scripts: generate_rust_analyzer.py: reduce cfg plumbing Tamir Duberstein
2026-01-21  1:16   ` Jesung Yang
2026-01-21 14:13     ` Tamir Duberstein
2026-01-21 23:12       ` Jesung Yang
2026-01-22 15:09         ` Tamir Duberstein
2026-01-20 19:27 ` Benno Lossin [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=DFTNX1DYBXWJ.24E4YYMAJSH9N@kernel.org \
    --to=lossin@kernel.org \
    --cc=a.hindborg@kernel.org \
    --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=nathan@kernel.org \
    --cc=nsc@kernel.org \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=tamird@kernel.org \
    --cc=tmgross@umich.edu \
    --cc=y.j3ms.n@gmail.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