From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Jul 10
Date: Sun, 12 Jul 2020 18:56:04 +0300 [thread overview]
Message-ID: <20200712155604.GA342822@smile.fi.intel.com> (raw)
In-Reply-To: <20200710183318.7b808092@canb.auug.org.au>
On Fri, Jul 10, 2020 at 06:33:18PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20200709:
>
> My fixes tree contains:
>
> dbf24e30ce2e ("device_cgroup: Fix RCU list debugging warning")
> b236d81d9e4f ("powerpc/boot/dts: Fix dtc "pciex" warnings")
>
> The kbuild tree still had its build failure for which I reverted a commit.
>
> The scmi tree lost its build failure.
>
> The drm tree gained a conflict against the drm-fixes tree.
>
> The security tree still had its build failure for which I applied a patch.
>
> The tip tree still had one build failure for which I reverted a commit
> and gained a conflict against the spi tree.
>
> The pidfd tree gained a conflict against the seccomp tree.
>
> The akpm-current tree lost its build failure but gained a conflict
> against the risc-v tree.
>
> Non-merge commits (relative to Linus' tree): 6231
> 7061 files changed, 371498 insertions(+), 144830 deletions(-)
I can't build it on Debian with Sparse enabled
CC init/main.o
init/main.c:760:20: warning: no previous prototype for ‘mem_encrypt_init’ [-Wmissing-prototypes]
760 | void __init __weak mem_encrypt_init(void) { }
| ^~~~~~~~~~~~~~~~
CHECK /home/andy/prj/linux-topic-uart/init/main.c
include/linux/compiler.h:309:16: error: typename in expression
include/linux/compiler.h:309:16: error: Expected ) in function call
include/linux/compiler.h:309:16: error: got :
...
(All READ_ONCE() entries fail)
Is it known issue?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2020-07-12 15:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-10 8:33 linux-next: Tree for Jul 10 Stephen Rothwell
2020-07-10 18:02 ` linux-next: Tree for Jul 10 (drivers/net/phy/mdio-thunder & mdio-mvusb) Randy Dunlap
2020-07-12 15:56 ` Andy Shevchenko [this message]
2020-07-12 22:01 ` linux-next: Tree for Jul 10 Stephen Rothwell
2020-07-13 2:19 ` Randy Dunlap
2020-07-13 2:26 ` Randy Dunlap
2020-07-13 2:27 ` Linus Torvalds
2020-07-13 2:33 ` Randy Dunlap
2020-07-13 11:01 ` Andy Shevchenko
-- strict thread matches above, loose matches on Subject: below --
2023-07-10 1:38 Stephen Rothwell
2019-07-10 11:10 Stephen Rothwell
2018-07-10 7:45 Stephen Rothwell
2017-07-10 5:58 Stephen Rothwell
2015-07-10 5:48 Stephen Rothwell
2014-07-10 7:20 Stephen Rothwell
2013-07-10 5:51 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=20200712155604.GA342822@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).