From: Danilo Krummrich <dakr@redhat.com>
To: Andreas Hindborg <a.hindborg@samsung.com>
Cc: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
Miguel Ojeda <ojeda@kernel.org>,
Philipp Stanner <pstanner@redhat.com>,
"rust-for-linux@vger.kernel.org" <rust-for-linux@vger.kernel.org>,
Greg KH <greg@kroah.com>
Subject: Re: RfL branch for PCI bindings
Date: Mon, 5 Feb 2024 12:40:04 +0100 [thread overview]
Message-ID: <d814c896-9700-42bb-846f-795d0c3e9680@redhat.com> (raw)
In-Reply-To: <87o7cztais.fsf@samsung.com>
On 2/2/24 11:40, Andreas Hindborg wrote:
>
> Miguel Ojeda <miguel.ojeda.sandonis@gmail.com> writes:
>
>> On Thu, Feb 1, 2024 at 4:02 PM Danilo Krummrich <dakr@redhat.com> wrote:
>>>
>>> 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.
>>
>> Thanks Danilo!
>>
>> My understanding from the meeting was that Andreas kindly agreed to
>> maintain a `rust-pci` branch in a compilable state (i.e. rebasing it
>> on top of e.g. `rust-next`). I am happy to create the branch already
>> if Andreas is ready, add it to the website, etc.
>>
>> Or if you (Danilo) prefer to drive the branch instead (e.g. because
>> you may have more bandwidth), that is also fine.
>
> Exactly. I am currently keeping the patches alive for the Rust NVMe
> driver that lives here [1], latest rebase here [2].
>
> I am not the original author of the Rust PCI patches. As far as I know,
> no one else is maintaining a copy of these patches on top of mainline
> (if there was, I would just use their work).
>
> I volunteer to extract these patches from the nvme tree into a separate
> pci tree and keep that rebased on mainline + accept fixes and features
> into that tree.
Thanks Andreas, very much appreciated! I think Philipp will start working
with this code soon.
>
> We can also do it the other way round and I would just rebase nvme on
> top of your pci tree, that is up to you.
>
> I don't have any plans of sending these patches upstream for now, since
> the NVMe driver is not welcome upstream. If/when Nova or another Rust
> project depending on pci is ready to merge, I would be happy to help
> upstream the pci patches, if that makes sense. Again, you could also do
> it yourself, that is completely up to you. Or perhaps the original
> authors are interested in helping with this - I do not know since it
> never came up.
The idea is to get an early version of Nova upstream and continue the
development upstream. Hence, once ready, we do intend to upstream the code
in this context. Of course, your help with that will be very welcome.
- Danilo
>
> We could start out in one configuration and then change later down the
> road if it becomes clear that another config would be more beneficial.
>
> Best regards,
> Andreas
>
>
> [1] https://rust-for-linux.com/nvme-driver
> [2] https://github.com/metaspace/linux/commits/nvme-6.7/
>
prev parent reply other threads:[~2024-02-05 11:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 15:02 RfL branch for PCI bindings Danilo Krummrich
2024-02-01 15:32 ` 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 [this message]
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=d814c896-9700-42bb-846f-795d0c3e9680@redhat.com \
--to=dakr@redhat.com \
--cc=a.hindborg@samsung.com \
--cc=greg@kroah.com \
--cc=miguel.ojeda.sandonis@gmail.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