From: Chris Suter <chris@sutes.me>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Geert Stappers <stappers@stappers.nl>, rust-for-linux@vger.kernel.org
Subject: Re: Fwd: Adding crates
Date: Tue, 29 Mar 2022 17:02:06 +1100 [thread overview]
Message-ID: <CAKfU0DLv3K7benXuofXqJwsgxUHA10bu8XWmyBZ0Z_PpZFMACg@mail.gmail.com> (raw)
In-Reply-To: <YkKXvnsvr0qz/pR2@kroah.com>
On Tue, Mar 29, 2022 at 4:23 PM Greg KH <gregkh@linuxfoundation.org> wrote:
>
> On Tue, Mar 29, 2022 at 08:38:29AM +1100, Chris Suter wrote:
> > I skimmed that thread, but unless I'm missing something, it seems to
> > be pretty much "don't do it", which doesn't work for me right now.
>
> Why not? What is the deadline?
>
> And what specific crates do you need and why? There is no "generic"
> solution here other than "do not do this."
I'm interested in quite a few crates but the first and perhaps most
significant would be futures. I'm not necessarily looking for a
"generic" solution at this point, any solution would do — just enough
to help me make a little progress and then maybe I could contribute
back later. I can probably figure it out myself, but I was hoping to
save some time.
— Chris
>
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2022-03-29 6:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKfU0DKvQYjhgiKN83+DZW3CQOkSEdQcy9nXUfFLVn1Uju6GkQ@mail.gmail.com>
2022-03-28 0:41 ` Fwd: Adding crates Chris Suter
2022-03-28 5:41 ` Geert Stappers
2022-03-28 21:38 ` Chris Suter
2022-03-29 5:23 ` Greg KH
2022-03-29 6:02 ` Chris Suter [this message]
2022-03-29 15:47 ` Miguel Ojeda
2022-03-30 0:03 ` Chris Suter
2022-03-30 4:31 ` Greg KH
2022-03-30 20:43 ` Kent Overstreet
2022-04-15 13:31 ` James Bottomley
2022-04-15 20:39 ` Kent Overstreet
2022-04-16 3:27 ` James Bottomley
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=CAKfU0DLv3K7benXuofXqJwsgxUHA10bu8XWmyBZ0Z_PpZFMACg@mail.gmail.com \
--to=chris@sutes.me \
--cc=gregkh@linuxfoundation.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=stappers@stappers.nl \
/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).