public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: broonie@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>,
	"Gary Guo" <gary@garyguo.net>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Linux Next Mailing List" <linux-next@vger.kernel.org>,
	"Martin Rodriguez Reboredo" <yakoyoku@gmail.com>,
	"Masahiro Yamada" <masahiroy@kernel.org>,
	"Michael Ellerman" <mpe@ellerman.id.au>,
	"Miguel Cano" <macanroj@gmail.com>,
	"Miguel Ojeda" <ojeda@kernel.org>,
	"Nick Desaulniers" <ndesaulniers@google.com>,
	"Sven Van Asbroeck" <thesven73@gmail.com>,
	"Tiago Lam" <tiagolam@gmail.com>,
	"Wedson Almeida Filho" <wedsonaf@google.com>
Subject: Re: linux-next: manual merge of the rust tree with the kbuild tree
Date: Mon, 15 Aug 2022 09:08:24 +1000	[thread overview]
Message-ID: <20220815090824.340d44bb@canb.auug.org.au> (raw)
In-Reply-To: <20220802233844.2613013-1-broonie@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 2317 bytes --]

Hi all,

On Wed,  3 Aug 2022 00:38:44 +0100 broonie@kernel.org wrote:
>
> Today's linux-next merge of the rust tree got a conflict in:
> 
>   Makefile
> 
> between commit:
> 
>   a6036a41bffba ("kbuild: drop support for CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE_O3")
> 
> from the kbuild tree and commit:
> 
>   fe24902ba8765 ("Kbuild: add Rust support")
> 
> from the rust tree.
> 
> I fixed it up (see below) and can carry the fix as necessary. This
> is now fixed as far as linux-next is concerned, but any non trivial
> conflicts should be mentioned to your upstream maintainer when your tree
> is submitted for merging.  You may also want to consider cooperating
> with the maintainer of the conflicting tree to minimise any particularly
> complex conflicts.
> 
> diff --cc Makefile
> index 60a7e3e8b4787,cd1d545f316bc..0000000000000
> --- a/Makefile
> +++ b/Makefile
> @@@ -758,10 -819,20 +822,17 @@@ KBUILD_CFLAGS	+= $(call cc-disable-warn
>   
>   ifdef CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE
>   KBUILD_CFLAGS += -O2
> + KBUILD_RUSTFLAGS += -Copt-level=2
>  -else ifdef CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE_O3
>  -KBUILD_CFLAGS += -O3
>  -KBUILD_RUSTFLAGS += -Copt-level=3
>   else ifdef CONFIG_CC_OPTIMIZE_FOR_SIZE
>   KBUILD_CFLAGS += -Os
> + KBUILD_RUSTFLAGS += -Copt-level=s
>   endif
>   
> + # Always set `debug-assertions` and `overflow-checks` because their default
> + # depends on `opt-level` and `debug-assertions`, respectively.
> + KBUILD_RUSTFLAGS += -Cdebug-assertions=$(if $(CONFIG_RUST_DEBUG_ASSERTIONS),y,n)
> + KBUILD_RUSTFLAGS += -Coverflow-checks=$(if $(CONFIG_RUST_OVERFLOW_CHECKS),y,n)
> + 
>   # Tell gcc to never replace conditional load with a non-conditional one
>   ifdef CONFIG_CC_IS_GCC
>   # gcc-10 renamed --param=allow-store-data-races=0 to
> @@@ -1098,7 -1178,7 +1178,8 @@@ export MODULES_NSDEPS := $(extmod_prefi
>   ifeq ($(KBUILD_EXTMOD),)
>   core-y			+= kernel/ certs/ mm/ fs/ ipc/ security/ crypto/
>   core-$(CONFIG_BLOCK)	+= block/
>  +core-$(CONFIG_IO_URING)	+= io_uring/
> + core-$(CONFIG_RUST)	+= rust/
>   
>   vmlinux-dirs	:= $(patsubst %/,%,$(filter %/, \
>   		     $(core-y) $(core-m) $(drivers-y) $(drivers-m) \

This is now a conflict between the rust tree and Linus' tree.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2022-08-14 23:08 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-02 23:38 linux-next: manual merge of the rust tree with the kbuild tree broonie
2022-08-03  9:28 ` Miguel Ojeda
2022-08-14 23:08 ` Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-17  9:38 Stephen Rothwell
2025-03-17 19:36 ` Miguel Ojeda
2025-03-31 23:58 ` Stephen Rothwell
2024-05-06  5:33 Stephen Rothwell
2024-05-06 10:19 ` Miguel Ojeda
2024-05-14  0:20 ` Stephen Rothwell
2022-09-27 18:16 broonie
2022-09-28 17:16 ` Miguel Ojeda
2022-10-04 22:23 ` Stephen Rothwell
2022-09-26 23:12 broonie
2022-09-27 12:47 ` Miguel Ojeda
2022-09-12  7:41 Stephen Rothwell
2022-04-05  3:14 Stephen Rothwell
2022-04-05  8:33 ` Miguel Ojeda
2022-03-17  6:02 Stephen Rothwell
2022-03-17  7:11 ` Miguel Ojeda
2022-01-17 23:51 Stephen Rothwell
2021-12-07  5:13 Stephen Rothwell
2021-12-03  5:20 Stephen Rothwell
2021-12-03  9:05 ` Miguel Ojeda
2021-10-15  7:24 Stephen Rothwell
2021-10-15 12:24 ` Miguel Ojeda
2021-10-28  9:09 ` Stephen Rothwell
2021-10-28 11:06   ` Miguel Ojeda
2021-10-06  5:46 Stephen Rothwell
2021-08-11  7:26 Stephen Rothwell
2021-08-11 17:04 ` Nick Desaulniers
2021-08-12  6:34   ` Stephen Rothwell
2021-03-29  7:32 Stephen Rothwell
2021-03-18  4:37 Stephen Rothwell
2021-03-18  5:04 ` Miguel Ojeda

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=20220815090824.340d44bb@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --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=boqun.feng@gmail.com \
    --cc=broonie@kernel.org \
    --cc=d0u9.su@outlook.com \
    --cc=davidgow@google.com \
    --cc=dsosnowski@dsosnowski.pl \
    --cc=dxu@dxuuu.xyz \
    --cc=gary@garyguo.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=macanroj@gmail.com \
    --cc=masahiroy@kernel.org \
    --cc=me@kloenk.de \
    --cc=miguel.ojeda.sandonis@gmail.com \
    --cc=mpe@ellerman.id.au \
    --cc=ndesaulniers@google.com \
    --cc=ojeda@kernel.org \
    --cc=thesven73@gmail.com \
    --cc=tiagolam@gmail.com \
    --cc=wedsonaf@google.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox