From: Philipp Stanner <pstanner@redhat.com>
To: rust-for-linux@vger.kernel.org
Cc: dakr@redhat.com
Subject: Intended folder structure for subsystem bindings
Date: Thu, 18 Jan 2024 10:20:12 +0100 [thread overview]
Message-ID: <241c57af61dc03c6f2f6bd90856908fcf84bb71a.camel@redhat.com> (raw)
Hi,
I'm having a look into potentially creating bindings for the PCI
subsystem.
I was wondering what the Rust infrastructure people had in mind here.
Should there be one folder per subsystem in rust/bindings?
Thanks,
P.
next reply other threads:[~2024-01-18 9:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 9:20 Philipp Stanner [this message]
2024-01-18 9:32 ` Intended folder structure for subsystem bindings Miguel Ojeda
2024-01-31 21:34 ` Trevor Gross
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=241c57af61dc03c6f2f6bd90856908fcf84bb71a.camel@redhat.com \
--to=pstanner@redhat.com \
--cc=dakr@redhat.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).