From: Danilo Krummrich <dakr@redhat.com>
To: Miguel Ojeda <ojeda@kernel.org>,
Andreas Hindborg <a.hindborg@samsung.com>
Cc: Philipp Stanner <pstanner@redhat.com>, rust-for-linux@vger.kernel.org
Subject: RfL branch for PCI bindings
Date: Thu, 1 Feb 2024 16:02:17 +0100 [thread overview]
Message-ID: <929f47e0-8aca-471d-b54f-26908321999b@redhat.com> (raw)
Hi Andreas and Miguel,
I'd like to come back to our discussion from the last "Rust for DRM" meeting regarding a
common "rust-pci" branch.
As discussed, in the context of the Nova project we are interested in using those bindings,
contribute some more (also in the context of Philipp's recent PCI work) and help moving the
code upstream.
With Nova we should have a driver project which should justify further efforts to upstream
the code.
- Danilo
next reply other threads:[~2024-02-01 15:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 15:02 Danilo Krummrich [this message]
2024-02-01 15:32 ` RfL branch for PCI bindings Greg KH
2024-02-01 18:54 ` Miguel Ojeda
2024-02-02 10:40 ` Andreas Hindborg
2024-02-03 18:31 ` Miguel Ojeda
2024-02-05 11:41 ` Danilo Krummrich
2024-02-07 21:54 ` Andreas Hindborg (Samsung)
2024-02-05 11:40 ` Danilo Krummrich
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=929f47e0-8aca-471d-b54f-26908321999b@redhat.com \
--to=dakr@redhat.com \
--cc=a.hindborg@samsung.com \
--cc=ojeda@kernel.org \
--cc=pstanner@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