From: Greg KH <gregkh@linuxfoundation.org>
To: Danilo Krummrich <dakr@redhat.com>
Cc: dri-devel@lists.freedesktop.org, nouveau@lists.freedesktop.org,
rust-for-linux@vger.kernel.org, airlied@redhat.com,
lyude@redhat.com, pstanner@redhat.com, ajanulgu@redhat.com,
mcanal@igalia.com, lina@asahilina.net, a.hindborg@samsung.com
Subject: Re: Nova and staging Rust abstractions
Date: Wed, 20 Mar 2024 19:17:54 +0100 [thread overview]
Message-ID: <2024032007-imprison-rejoicing-e925@gregkh> (raw)
In-Reply-To: <Zfsj0_tb-0-tNrJy@cassiopeiae>
On Wed, Mar 20, 2024 at 06:58:43PM +0100, Danilo Krummrich wrote:
> @Greg, can you please have a first quick look at rust-device [5]?
If they are sent as patches to review, yes, I can get to them as part of
my normal patch review cycle. Otherwise I have no cyeles to dig through
random github trees...
thanks,
greg k-h
prev parent reply other threads:[~2024-03-20 18:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-20 17:58 Nova and staging Rust abstractions Danilo Krummrich
2024-03-20 18:17 ` Greg KH [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=2024032007-imprison-rejoicing-e925@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=a.hindborg@samsung.com \
--cc=airlied@redhat.com \
--cc=ajanulgu@redhat.com \
--cc=dakr@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=lina@asahilina.net \
--cc=lyude@redhat.com \
--cc=mcanal@igalia.com \
--cc=nouveau@lists.freedesktop.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).