From: Alex Gaynor <alex.gaynor@gmail.com>
To: Carlos <carloscarral13@gmail.com>
Cc: rust-for-linux <rust-for-linux@vger.kernel.org>
Subject: Re: Exposing semaphores
Date: Mon, 26 Apr 2021 20:08:43 -0400 [thread overview]
Message-ID: <CAFRnB2XTJ_bSoMXz44McH8153rAW0+h--zN_+W-hw+gMsEL95Q@mail.gmail.com> (raw)
In-Reply-To: <YIdUf1C5VtWn/D2G@localhost.localdomain>
It sounds like you already identified it, but yup, that'd be my major
piece of advice, follow the conventions and traits use in the other
sync/ locking types:
https://github.com/Rust-for-Linux/linux/tree/rust/rust/kernel/sync
Glad to hear you're already diving into scull!
Cheers,
Alex
On Mon, Apr 26, 2021 at 8:02 PM Carlos <carloscarral13@gmail.com> wrote:
>
> 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?
>
>
>
--
All that is necessary for evil to succeed is for good people to do nothing.
next prev parent reply other threads:[~2021-04-27 0:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 0:02 Exposing semaphores Carlos
2021-04-27 0:08 ` Alex Gaynor [this message]
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=CAFRnB2XTJ_bSoMXz44McH8153rAW0+h--zN_+W-hw+gMsEL95Q@mail.gmail.com \
--to=alex.gaynor@gmail.com \
--cc=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;
as well as URLs for NNTP newsgroup(s).