From: Nathan Chancellor <nathan@kernel.org>
To: broonie@kernel.org
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
llvm@lists.linux.dev
Subject: Re: linux-next: Tree for Dec 14
Date: Tue, 14 Dec 2021 17:37:16 -0700 [thread overview]
Message-ID: <Ybk4vF68Uhsd/8JH@archlinux-ax161> (raw)
In-Reply-To: <20211214223228.1745315-1-broonie@kernel.org>
Hi Mark,
On Tue, Dec 14, 2021 at 10:32:22PM +0000, broonie@kernel.org wrote:
> Hi all,
>
> News: Releases may or may not happen over the next few days since I'm
> getting a vacciene dose tomorrow.
>
> Changes since 20211213:
>
> The drm-intel tree gained a conflict with the drm-intel-fixes tree.
>
> The dmaengine tree gained a conflict with the dmaengine-fixes tree.
>
> Non-merge commits (relative to Linus' tree): 6251
> 6873 files changed, 291130 insertions(+), 138903 deletions(-)
Was there a conflict in mm/migrate.c with this release? It looks like
the ptl assignment was dropped in commit fd93c9fe58cc ("Merge branch
'akpm-current/current'") but I do not see that in any of the individual
mm/migrate.c commits. I noticed this because Clang warns now:
mm/migrate.c:347:14: error: variable 'ptl' is uninitialized when used here [-Werror,-Wuninitialized]
spin_unlock(ptl);
^~~
mm/migrate.c:340:17: note: initialize the variable 'ptl' to silence this warning
spinlock_t *ptl;
^
= NULL
1 error generated.
Cheers,
Nathan
next prev parent reply other threads:[~2021-12-15 0:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-14 22:32 linux-next: Tree for Dec 14 broonie
2021-12-15 0:37 ` Nathan Chancellor [this message]
2021-12-15 1:49 ` linux-next: Tree for Dec 14 (arch/x86/kernel/apic/msi.o) Randy Dunlap
2021-12-15 19:25 ` Thomas Gleixner
2021-12-15 15:54 ` linux-next: Tree for Dec 14 Andy Shevchenko
2021-12-15 18:06 ` Mark Brown
2021-12-15 18:40 ` Andy Shevchenko
2021-12-15 18:43 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2023-12-14 5:33 Stephen Rothwell
2022-12-14 3:21 Stephen Rothwell
2020-12-14 10:20 Stephen Rothwell
2018-12-14 7:18 Stephen Rothwell
2018-12-15 15:51 ` Guenter Roeck
2017-12-14 7:06 Stephen Rothwell
2016-12-14 4:22 Stephen Rothwell
2016-12-14 16:25 ` Paul Gortmaker
2016-12-14 20:07 ` Heiko Carstens
2015-12-14 6:18 Stephen Rothwell
2012-12-14 7:42 Stephen Rothwell
2011-12-14 7:26 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=Ybk4vF68Uhsd/8JH@archlinux-ax161 \
--to=nathan@kernel.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=llvm@lists.linux.dev \
/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).