From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Greg KH <greg@kroah.com>, Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Hang Lu <hangl@codeaurora.org>, Li Li <dualli@google.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Marco Ballesio <balejs@google.com>,
Miguel Ojeda <ojeda@kernel.org>, Todd Kjos <tkjos@google.com>,
Wedson Almeida Filho <wedsonaf@google.com>
Subject: Re: linux-next: manual merge of the rust tree with the char-misc tree
Date: Fri, 16 Apr 2021 14:31:50 +0200 [thread overview]
Message-ID: <CANiq72mGZnWRS4Yu6iUY2jE2zaNHEz5a5gjmqZtBFEVTfNxRiA@mail.gmail.com> (raw)
In-Reply-To: <20210416175806.2acd314b@canb.auug.org.au>
Hi Stephen,
On Fri, Apr 16, 2021 at 9:58 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> from the char-misc tree and commit:
>
> 1fed5dee5fbb ("Android: Binder IPC in Rust (WIP)")
>
> from the rust tree.
If you prefer, I can take out the binder bits from rust-next since
they will be submitted separately anyhow (i.e. they would eventually
go through the char-misc/Android tree after/if Rust support lands).
Cheers,
Miguel
next prev parent reply other threads:[~2021-04-16 12:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-16 7:58 linux-next: manual merge of the rust tree with the char-misc tree Stephen Rothwell
2021-04-16 8:10 ` Greg KH
2021-04-16 8:26 ` Stephen Rothwell
2021-04-16 12:31 ` Miguel Ojeda [this message]
2022-05-16 7:13 Stephen Rothwell
2022-05-16 7:49 ` Greg KH
2022-05-16 8:18 ` Miguel Ojeda
2022-05-16 8:27 ` Greg KH
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=CANiq72mGZnWRS4Yu6iUY2jE2zaNHEz5a5gjmqZtBFEVTfNxRiA@mail.gmail.com \
--to=miguel.ojeda.sandonis@gmail.com \
--cc=arnd@arndb.de \
--cc=balejs@google.com \
--cc=dualli@google.com \
--cc=greg@kroah.com \
--cc=gregkh@linuxfoundation.org \
--cc=hangl@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tkjos@google.com \
--cc=wedsonaf@google.com \
/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).