From: Kent Overstreet <kent.overstreet@linux.dev>
To: FUJITA Tomonori <tomo@exabit.dev>
Cc: rust-for-linux@vger.kernel.org, netdev@vger.kernel.org,
linux-crypto@vger.kernel.org,
FUJITA Tomonori <fujita.tomonori@gmail.com>
Subject: Re: [PATCH 1/2] rust: add synchronous message digest support
Date: Mon, 15 May 2023 02:11:52 -0400 [thread overview]
Message-ID: <ZGHNKCY/2C5buW7O@moria.home.lan> (raw)
In-Reply-To: <010101881db037b4-c8c941a9-c482-4759-9c07-b8bf645d96ed-000000@us-west-2.amazonses.com>
On Mon, May 15, 2023 at 04:34:27AM +0000, FUJITA Tomonori wrote:
> From: FUJITA Tomonori <fujita.tomonori@gmail.com>
>
> Adds abstractions for crypto shash.
>
> Signed-off-by: FUJITA Tomonori <fujita.tomonori@gmail.com>
> ---
> rust/bindings/bindings_helper.h | 1 +
> rust/helpers.c | 24 +++++++
> rust/kernel/crypto.rs | 108 ++++++++++++++++++++++++++++++++
> rust/kernel/lib.rs | 2 +
I think in the long run we're going to need Rust bindings located right
next to the .c files they're wrapping. Certainly modules will.
next prev parent reply other threads:[~2023-05-15 6:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230515043353.2324288-1-tomo@exabit.dev>
2023-05-15 4:34 ` [PATCH 1/2] rust: add synchronous message digest support FUJITA Tomonori
2023-05-15 6:11 ` Kent Overstreet [this message]
2023-05-16 5:52 ` Eric Biggers
2023-05-16 8:25 ` FUJITA Tomonori
2023-05-15 4:34 ` [PATCH 2/2] rust: add socket support FUJITA Tomonori
2023-05-15 14:14 ` Andrew Lunn
2023-05-16 5:43 ` FUJITA Tomonori
2023-05-16 12:07 ` Andrew Lunn
2023-05-16 17:08 ` Wedson Almeida Filho
2023-05-17 2:46 ` FUJITA Tomonori
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=ZGHNKCY/2C5buW7O@moria.home.lan \
--to=kent.overstreet@linux.dev \
--cc=fujita.tomonori@gmail.com \
--cc=linux-crypto@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tomo@exabit.dev \
/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