[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20211006164652.28b82d57@canb.auug.org.au>
Date: Wed, 6 Oct 2021 16:46:52 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>,
Masahiro Yamada <masahiroy@...nel.org>
Cc: Adam Bratschi-Kaye <ark.email@...il.com>,
Alex Gaynor <alex.gaynor@...il.com>,
Ayaan Zaidi <zaidi.ayaan@...il.com>,
Boqun Feng <boqun.feng@...il.com>,
Boris-Chengbiao Zhou <bobo1239@....de>,
Douglas Su <d0u9.su@...look.com>, Finn Behrens <me@...enk.de>,
Fox Chen <foxhlchen@...il.com>, Gary Guo <gary@...yguo.net>,
Geoffrey Thomas <geofft@...reload.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Michael Ellerman <mpe@...erman.id.au>,
Miguel Ojeda <ojeda@...nel.org>,
Sumera Priyadarsini <sylphrenadin@...il.com>,
Sven Van Asbroeck <thesven73@...il.com>,
Wedson Almeida Filho <wedsonaf@...gle.com>,
Yuki Okushi <jtitor@...6.org>
Subject: linux-next: manual merge of the rust tree with the kbuild tree
Hi all,
Today's linux-next merge of the rust tree got a conflict in:
scripts/kconfig/confdata.c
between several commits, including
2836b7a7bd05 ("[for -next only] kconfig: generate include/generated/rustc_cfg")
from the kbuild tree and commit:
dc08d49444e9 ("Kbuild: add Rust support")
from the rust tree.
I fixed it up (as per Masahiro Yamada's suggestion, I used the version
from the kbuild tree) 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.
--
Cheers,
Stephen Rothwell
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists