Rust for Linux List
 help / color / mirror / Atom feed
From: "Andreas Hindborg (Samsung)" <nmi@metaspace.dk>
To: Danilo Krummrich <dakr@redhat.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: Wed, 07 Feb 2024 22:54:43 +0100	[thread overview]
Message-ID: <87zfwcrkyx.fsf@metaspace.dk> (raw)
In-Reply-To: <f60af824-633d-4e9d-b20e-7fb9911d9e0e@redhat.com>


Danilo Krummrich <dakr@redhat.com> writes:

> On 2/3/24 19:31, Miguel Ojeda wrote:
>> On Fri, Feb 2, 2024 at 11:40 AM Andreas Hindborg <a.hindborg@samsung.com> wrote:
>>>
>>> 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.
>> +1, let's start with what we discussed -- we can change the
>> arrangement whenever needed.
>> I have created the branch in our repository:
>>      https://github.com/Rust-for-Linux/linux/tree/rust-pci
>> And added it to the website:
>>      https://rust-for-linux.com/branches#rust-pci
>> Please feel free to push to the branch as you see fit -- thanks Andreas!
>
> +1
>
> And thanks Miguel for setting things up!
>
> @Andreas: Please let us know once you pushed the patches.

They are up. Please not that they are not high quality, lots of TODO and
missing safety comments.

NVMe rebased on top is here [1]

Let me know if you have any questions!

Best regards,
Andreas


[1] https://github.com/metaspace/linux/tree/rnvme-for-6.8


  reply	other threads:[~2024-02-07 22:03 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) [this message]
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=87zfwcrkyx.fsf@metaspace.dk \
    --to=nmi@metaspace.dk \
    --cc=dakr@redhat.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