From: Heiko Carstens <hca@linux.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Alex Gaynor <alex.gaynor@gmail.com>,
Geoffrey Thomas <geofft@ldpreload.com>,
Finn Behrens <me@kloenk.de>,
Wedson Almeida Filho <wedsonaf@google.com>,
Adam Bratschi-Kaye <ark.email@gmail.com>,
Miguel Ojeda <ojeda@kernel.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Vasily Gorbik <gor@linux.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>
Subject: Re: linux-next: Tree for Mar 19
Date: Fri, 19 Mar 2021 15:30:31 +0100 [thread overview]
Message-ID: <YFS1h6h+71sRlwFR@osiris> (raw)
In-Reply-To: <20210319175950.509fcbd0@canb.auug.org.au>
On Fri, Mar 19, 2021 at 05:59:50PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Warning: Some of the branches in linux-next may still based on v5.12-rc1,
> so please be careful if you are trying to bisect a bug.
>
> News: if your -next included tree is based on Linus' tree tag
> v5.12-rc1{,-dontuse} (or somewhere between v5.11 and that tag), please
> consider rebasing it onto v5.12-rc2. Also, please check any branches
> merged into your branch.
>
> Changes since 20210318:
>
> The net-next tree gained a conflict against the net tree.
>
> The amdgpu tree gained a build failure so I used the version from
> next-20210318.
>
> The security tree gained a conflict against the ext3 tree.
>
> The rcu tree lost its build failure.
>
> The akpm-current tree still had its build failure for which I applied
> a hack.
>
> The akpm tree gained a conflict against the security tre.
>
> Non-merge commits (relative to Linus' tree): 5051
> 4781 files changed, 329814 insertions(+), 90904 deletions(-)
...
> Merging rust/rust-next (8ef6f74a3571 Rust support)
This breaks now on s390 with commit 8ef6f74a3571 ("Rust support").
make modules_install / depmod now fails with:
depmod: WARNING: /.../lib/modules/5.12.0-rc3-00001-g8ef6f74a3571/kernel/drivers/s390/scsi/zfcp.ko needs unknown symbol
for every module (yes, the line is complete).
next prev parent reply other threads:[~2021-03-19 14:31 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 6:59 linux-next: Tree for Mar 19 Stephen Rothwell
2021-03-19 14:30 ` Heiko Carstens [this message]
2021-03-20 5:27 ` Stephen Rothwell
2021-03-20 6:07 ` Miguel Ojeda
2021-03-20 6:49 ` Miguel Ojeda
2021-03-20 6:58 ` Miguel Ojeda
2021-03-21 12:30 ` Michael Ellerman
2021-03-21 15:57 ` Miguel Ojeda
-- strict thread matches above, loose matches on Subject: below --
2026-03-19 14:52 Mark Brown
2025-03-19 10:15 Stephen Rothwell
2024-03-19 1:49 Stephen Rothwell
2020-03-19 7:39 Stephen Rothwell
2019-03-19 5:12 Stephen Rothwell
2018-03-19 8:02 Stephen Rothwell
2015-03-19 7:28 Stephen Rothwell
2014-03-19 7:18 Stephen Rothwell
2014-03-19 7:18 ` Stephen Rothwell
2013-03-19 5:42 Sedat Dilek
2013-03-19 5:47 ` Stephen Rothwell
2013-03-19 5:53 ` Sedat Dilek
2013-03-19 5:54 ` Stephen Rothwell
2013-03-19 6:00 ` Sedat Dilek
2013-03-19 10:24 ` Sedat Dilek
2013-03-19 4:14 Stephen Rothwell
2013-03-19 4:14 ` Stephen Rothwell
2012-03-19 7:48 Stephen Rothwell
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=YFS1h6h+71sRlwFR@osiris \
--to=hca@linux.ibm.com \
--cc=alex.gaynor@gmail.com \
--cc=ark.email@gmail.com \
--cc=borntraeger@de.ibm.com \
--cc=geofft@ldpreload.com \
--cc=gor@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=me@kloenk.de \
--cc=ojeda@kernel.org \
--cc=sfr@canb.auug.org.au \
--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 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.