All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: "Linus Torvalds" <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org,
	"Adam Bratschi-Kaye" <ark.email@gmail.com>,
	"Alex Gaynor" <alex.gaynor@gmail.com>,
	"Antonio Terceiro" <antonio.terceiro@linaro.org>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"Boqun Feng" <boqun.feng@gmail.com>,
	"Boris-Chengbiao Zhou" <bobo1239@web.de>,
	"Daniel Xu" <dxu@dxuuu.xyz>,
	"Dariusz Sosnowski" <dsosnowski@dsosnowski.pl>,
	"David Gow" <davidgow@google.com>,
	"Douglas Su" <d0u9.su@outlook.com>, "Finn Behrens" <me@kloenk.de>,
	"Fox Chen" <foxhlchen@gmail.com>, "Gary Guo" <gary@garyguo.net>,
	"Geert Stappers" <stappers@stappers.nl>,
	"Geoffrey Thomas" <geofft@ldpreload.com>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Jiapeng Chong" <jiapeng.chong@linux.alibaba.com>,
	"Joe Perches" <joe@perches.com>,
	"John Baublitz" <john.m.baublitz@gmail.com>,
	"Julian Merkle" <me@jvmerkle.de>,
	"Léo Lanteri Thauvin" <leseulartichaut@gmail.com>,
	"Maciej Falkowski" <m.falkowski@samsung.com>,
	"Martin Rodriguez Reboredo" <yakoyoku@gmail.com>,
	"Matthew Bakhtiari" <dev@mtbk.me>,
	"Matthew Wilcox" <willy@infradead.org>,
	"Michael Ellerman" <mpe@ellerman.id.au>,
	"Miguel Cano" <macanroj@gmail.com>,
	"Miguel Ojeda" <ojeda@kernel.org>,
	"Milan Landaverde" <milan@mdaverde.com>,
	"Morgan Bartlett" <mjmouse9999@gmail.com>,
	"Nándor István Krácser" <bonifaido@gmail.com>,
	"Nick Desaulniers" <ndesaulniers@google.com>,
	"Niklas Mohrin" <dev@niklasmohrin.de>,
	"Petr Mladek" <pmladek@suse.com>,
	"Sumera Priyadarsini" <sylphrenadin@gmail.com>,
	"Sven Van Asbroeck" <thesven73@gmail.com>,
	"Tiago Lam" <tiagolam@gmail.com>,
	"Viktor Garske" <viktor@v-gar.de>,
	"Wedson Almeida Filho" <wedsonaf@gmail.com>,
	"Wei Liu" <wei.liu@kernel.org>, "Wu XiangCheng" <bobwxc@email.cn>,
	"Yuki Okushi" <jtitor@2k36.org>
Subject: Re: [GIT PULL] Rust introduction for v6.1-rc1
Date: Sat, 1 Oct 2022 15:50:39 -0700	[thread overview]
Message-ID: <202210011547.A456D4679@keescook> (raw)
In-Reply-To: <CAK7LNAQ2xBLG_aSDm64SSYRBOBKwhJnZ6UDg8ycAezATVToFLg@mail.gmail.com>

On Sun, Oct 02, 2022 at 05:21:17AM +0900, Masahiro Yamada wrote:
> On Sun, Oct 2, 2022 at 12:59 AM Kees Cook <keescook@chromium.org> wrote:
> >
> > Hi Linus,
> >
> > Please pull the initial Rust support for v6.1-rc1. The tree has a recent
> > base, but has fundamentally been in linux-next for a year and a half[1].
> > It's been updated based on feedback from the Kernel Maintainer's Summit,
> > and to gain recent Reviewed-by: tags. Miguel is the primary maintainer,
> > with me helping where needed/wanted. Our plan is for the tree to switch to
> > the standard non-rebasing practice once this initial infrastructure series
> > lands. The contents are the absolute minimum to get Rust code building
> > in the kernel, with many more interfaces[2] (and drivers[3]) on the way.
> >
> > Expected conflicts are minimal:
> > - docs-next: https://lore.kernel.org/lkml/87czbegets.fsf@meer.lwn.net/
> 
> 
> Also, conflicts against the Kbuild tree.

Ah, yes. Apologies; I missed this while checking the list. The latest
I found are from 9/28:
https://lore.kernel.org/linux-next/20220927181647.487727-1-broonie@kernel.org/
Miguel verified the conflict resolution at the time.

> linux-next 20220930 fails to build with CONFIG_RUST=y because the merge
> conflicts between Kbuild and Rust trees were not correctly resolved.

Ah, did something change between 28 and 30?

> I will try my best to address merge conflicts when I send my pull request.

Thank you!

-- 
Kees Cook

  reply	other threads:[~2022-10-01 22:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-01 15:58 [GIT PULL] Rust introduction for v6.1-rc1 Kees Cook
2022-10-01 20:21 ` Masahiro Yamada
2022-10-01 22:50   ` Kees Cook [this message]
2022-10-01 23:01     ` Miguel Ojeda
2022-10-04  5:32 ` Xi Ruoyao
2022-10-04  6:40   ` Boqun Feng

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=202210011547.A456D4679@keescook \
    --to=keescook@chromium.org \
    --cc=alex.gaynor@gmail.com \
    --cc=antonio.terceiro@linaro.org \
    --cc=ark.email@gmail.com \
    --cc=bjorn3_gh@protonmail.com \
    --cc=bobo1239@web.de \
    --cc=bobwxc@email.cn \
    --cc=bonifaido@gmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=d0u9.su@outlook.com \
    --cc=davidgow@google.com \
    --cc=dev@mtbk.me \
    --cc=dev@niklasmohrin.de \
    --cc=dsosnowski@dsosnowski.pl \
    --cc=dxu@dxuuu.xyz \
    --cc=foxhlchen@gmail.com \
    --cc=gary@garyguo.net \
    --cc=geofft@ldpreload.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jiapeng.chong@linux.alibaba.com \
    --cc=joe@perches.com \
    --cc=john.m.baublitz@gmail.com \
    --cc=jtitor@2k36.org \
    --cc=leseulartichaut@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.falkowski@samsung.com \
    --cc=macanroj@gmail.com \
    --cc=masahiroy@kernel.org \
    --cc=me@jvmerkle.de \
    --cc=me@kloenk.de \
    --cc=milan@mdaverde.com \
    --cc=mjmouse9999@gmail.com \
    --cc=mpe@ellerman.id.au \
    --cc=ndesaulniers@google.com \
    --cc=ojeda@kernel.org \
    --cc=pmladek@suse.com \
    --cc=stappers@stappers.nl \
    --cc=sylphrenadin@gmail.com \
    --cc=thesven73@gmail.com \
    --cc=tiagolam@gmail.com \
    --cc=torvalds@linux-foundation.org \
    --cc=viktor@v-gar.de \
    --cc=wedsonaf@gmail.com \
    --cc=wei.liu@kernel.org \
    --cc=willy@infradead.org \
    --cc=yakoyoku@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.