From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Hadar Gat <Hadar.Gat@arm.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
linux-s390 <linux-s390@vger.kernel.org>,
Gilad Ben-Yossef <gilad@benyossef.com>,
Ofir Drang <Ofir.Drang@arm.com>, nd <nd@arm.com>
Subject: Re: linux-next: Tree for Apr 20
Date: Mon, 20 Apr 2020 09:30:50 +0200 [thread overview]
Message-ID: <9b70262a-10b5-beb5-e058-3a0a2fa0fb8f@de.ibm.com> (raw)
In-Reply-To: <DB6PR0802MB2533E416D358177D5CA53564E9D40@DB6PR0802MB2533.eurprd08.prod.outlook.com>
On 20.04.20 09:23, Hadar Gat wrote:
>
>> On 20.04.20 06:26, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> Changes since 20200417:
>>>
>>> My fixes tree is empty again.
>>>
>>> The qcom tree still had its build failure for which I reverted a commit.
>>>
>>> The crypto tree still has its build failure for which I reverted 5 commits.
>>>
>>> The drm-misc tree gained a build failure for which I disabled a
>>> COMPILE_TEST setting.
>>>
>>> The sound-asoc tree still has its build failures so I used the version
>>> from next-20200414.
>>>
>>> The ipmi tree gained a build failure for which I applied a patch.
>>>
>>> Non-merge commits (relative to Linus' tree): 2732
>>> 3544 files changed, 76515 insertions(+), 37271 deletions(-)
>>
>> s390 defconfig still does not compile. While the media kconfig problem is
>> gone I now have
>>
>> CC [M] drivers/char/hw_random/cctrng.o
>> drivers/char/hw_random/cctrng.c: In function ‘cc_trng_compwork_handler’:
>> drivers/char/hw_random/cctrng.c:334:49: error: ‘fips_enabled’ undeclared
>> (first use in this function); did you mean ‘vdso_enabled’?
>> 334 | if (CC_REG_FLD_GET(RNG_ISR, CRNGT_ERR, isr) && fips_enabled) {
>> | ^~~~~~~~~~~~
>> | vdso_enabled
>> drivers/char/hw_random/cctrng.c:334:49: note: each undeclared identifier is
>> reported only once for each function it appears in
>> drivers/char/hw_random/cctrng.c:335:3: error: implicit declaration of
>> function ‘fips_fail_notify’ [-Werror=implicit-function-declaration]
>> 335 | fips_fail_notify();
>> | ^~~~~~~~~~~~~~~~
>> cc1: some warnings being treated as errors
>>
>> Can we maybe make this driver depend on ARM?
>
> Hi,
> This compilation issue is already fixed.
> It was pushed few days ago and is waiting to be applied.
> https://lore.kernel.org/linux-crypto/096db769-a508-b0fa-f018-2c4c807061cb@infradead.org/
Herbert,
can these things be applied in a timely fashion? This DOES break several automated test
cases that usually run on linux-next.
next prev parent reply other threads:[~2020-04-20 7:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 4:26 linux-next: Tree for Apr 20 Stephen Rothwell
2020-04-20 7:14 ` Christian Borntraeger
2020-04-20 7:23 ` Hadar Gat
2020-04-20 7:30 ` Christian Borntraeger [this message]
2020-04-20 7:25 ` Stephen Rothwell
2020-04-20 15:21 ` linux-next: Tree for Apr 20 (media Kconfig warning) Randy Dunlap
2020-04-20 15:45 ` Randy Dunlap
2020-04-20 15:29 ` linux-next: Tree for Apr 20 (objtool warning) Randy Dunlap
2020-04-20 15:53 ` Josh Poimboeuf
2020-04-20 16:14 ` Randy Dunlap
2020-04-20 16:33 ` linux-next: Tree for Apr 20 (media: usbvision) Randy Dunlap
-- strict thread matches above, loose matches on Subject: below --
2023-04-20 15:44 linux-next: Tree for Apr 20 broonie
2022-04-20 7:50 Stephen Rothwell
2021-04-20 9:47 Stephen Rothwell
2021-04-20 12:02 ` Andy Shevchenko
2021-04-20 12:19 ` Andy Shevchenko
2021-04-20 12:35 ` Andy Shevchenko
2018-04-20 6:11 Stephen Rothwell
2017-04-20 6:43 Stephen Rothwell
2016-04-20 5:12 Stephen Rothwell
2015-04-20 5:45 Stephen Rothwell
2012-04-20 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=9b70262a-10b5-beb5-e058-3a0a2fa0fb8f@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=Hadar.Gat@arm.com \
--cc=Ofir.Drang@arm.com \
--cc=gilad@benyossef.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=nd@arm.com \
--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).