rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Gary Guo <gary@garyguo.net>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
	"Alex Gaynor" <alex.gaynor@gmail.com>,
	"Wedson Almeida Filho" <wedsonaf@gmail.com>,
	"Boqun Feng" <boqun.feng@gmail.com>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"Benno Lossin" <benno.lossin@proton.me>,
	"Andreas Hindborg" <a.hindborg@samsung.com>,
	"Alice Ryhl" <aliceryhl@google.com>,
	"Dirk Behme" <dirk.behme@de.bosch.com>,
	rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] kbuild: rust: auto generate rust helper exports
Date: Mon, 19 Aug 2024 15:03:58 +0200	[thread overview]
Message-ID: <CANiq72mGbdKRKuEPbmC7TLOJVXMmpvap8Vinpex-TCtorKaUVw@mail.gmail.com> (raw)
In-Reply-To: <20240817165302.3852499-1-gary@garyguo.net>

On Sat, Aug 17, 2024 at 6:54 PM Gary Guo <gary@garyguo.net> wrote:
>
> This removes the need for explicit exporting all symbols.
>
> Generate helper exports similar to what's currently done for Rust
> crates. These helpers are exclusively called from within Rust code
> and therefore can be treated similar as other Rust symbols.
>
> Signed-off-by: Gary Guo <gary@garyguo.net>

Applied to `rust-next` -- thanks everyone!

    [ Fixed dependency path, reworded slightly, edited comment a bit and
      rebased on top of the changes made when applying Andreas' patch
      (e.g. no `README.md` anymore, so moved the edits).  - Miguel ]

Cheers,
Miguel

  parent reply	other threads:[~2024-08-19 13:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-17 16:51 [PATCH v2] kbuild: rust: auto generate rust helper exports Gary Guo
2024-08-18  0:47 ` Boqun Feng
2024-08-18 23:40   ` Miguel Ojeda
2024-08-18 23:56     ` Gary Guo
2024-08-19  0:17       ` Miguel Ojeda
2024-08-19  0:27         ` Boqun Feng
2024-08-19  0:57     ` Boqun Feng
2024-08-19 13:03 ` Miguel Ojeda [this message]
2024-09-25 20:49   ` Sami Tolvanen

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=CANiq72mGbdKRKuEPbmC7TLOJVXMmpvap8Vinpex-TCtorKaUVw@mail.gmail.com \
    --to=miguel.ojeda.sandonis@gmail.com \
    --cc=a.hindborg@samsung.com \
    --cc=alex.gaynor@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=benno.lossin@proton.me \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=dirk.behme@de.bosch.com \
    --cc=gary@garyguo.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=wedsonaf@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;
as well as URLs for NNTP newsgroup(s).