From: Carlos <carloscarral13@gmail.com>
To: rust-for-linux@vger.kernel.org
Subject: Exposing semaphores
Date: Mon, 26 Apr 2021 19:02:07 -0500 [thread overview]
Message-ID: <YIdUf1C5VtWn/D2G@localhost.localdomain> (raw)
Hello to all,
I recently began assessing what functionality from the kernel is missing
for implementing a basic scull driver.
Semaphores are the first missing primitive that caught my attention, and
being such an important part of the kernel itself, I will make exposing
this functionality my first priority instead.
It should be pretty straightforward, following the stablished convention of
leveraging the kernel API.
Any comments before I dig in?
next reply other threads:[~2021-04-27 0:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 0:02 Carlos [this message]
2021-04-27 0:08 ` Exposing semaphores Alex Gaynor
2021-04-27 0:12 ` Wedson Almeida Filho
2021-04-27 1:43 ` Samantha Miller
2021-04-27 11:00 ` Sven Van Asbroeck
2021-04-27 10:18 ` Sven Van Asbroeck
2021-04-27 10:58 ` Greg KH
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=YIdUf1C5VtWn/D2G@localhost.localdomain \
--to=carloscarral13@gmail.com \
--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