From: Palmer Dabbelt <palmerdabbelt@google.com>
To: Atish Patra <Atish.Patra@wdc.com>
Cc: anders.roxell@linaro.org, Stephen Rothwell <sfr@canb.auug.org.au>,
anup@brainfault.org, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for Aug 27
Date: Thu, 27 Aug 2020 10:03:53 -0700 (PDT) [thread overview]
Message-ID: <mhng-16126c08-fe1d-43bf-bd48-9f1cdcdb5a57@palmerdabbelt-glaptop1> (raw)
In-Reply-To: <fa8a133517704eff9b0f2369c1b7b5bbc8517916.camel@wdc.com>
On Thu, 27 Aug 2020 10:02:57 PDT (-0700), Atish Patra wrote:
> On Thu, 2020-08-27 at 10:37 +0200, Anders Roxell wrote:
>> On Thu, 27 Aug 2020 at 07:11, Stephen Rothwell <sfr@canb.auug.org.au>
>> wrote:
>> > Hi all,
>> >
>> > News: There will be no linux-next releases next Monday or Tuesday.
>> >
>> > Changes since 20200826:
>> >
>> > The net-next tree gained a conflict against the net tree.
>> >
>> > Non-merge commits (relative to Linus' tree): 2901
>> > 3429 files changed, 100496 insertions(+), 37081 deletions(-)
>> >
>>
>> I built riscv on todays tag and I see this error:
>> ../arch/riscv/kernel/setup.c: In function ‘setup_arch’:
>> ../arch/riscv/kernel/setup.c:74:2: error: implicit declaration of
>> function ‘early_ioremap_setup’; did you mean ‘early_memtest’?
>> [-Werror=implicit-function-declaration]
>> early_ioremap_setup();
>> ^~~~~~~~~~~~~~~~~~~
>> early_memtest
>> cc1: some warnings being treated as errors
>>
>> I think its due to commit 3d109b0e0949 ("RISC-V: Add early ioremap
>> support")
>>
>
> Yes. For some reason, I never get this with the UEFI support series
> applied on top 5.9-rc2 in my tree. But I get this error with linux-next
> tree.
>
>> It builds with this fix:
>>
>> diff --git a/arch/riscv/kernel/setup.c b/arch/riscv/kernel/setup.c
>> index 5ab185130cae..41ef96d0d97a 100644
>> --- a/arch/riscv/kernel/setup.c
>> +++ b/arch/riscv/kernel/setup.c
>> @@ -19,6 +19,7 @@
>> #include <linux/smp.h>
>>
>> #include <asm/cpu_ops.h>
>> +#include <asm/early_ioremap.h>
>> #include <asm/setup.h>
>> #include <asm/sections.h>
>> #include <asm/sbi.h>
>>
>>
>
> This fix solves the problem. Thanks.
> @palmer: Do you want me to update the patch and send v7 ?
That'd be great, thanks!
>
>
>> Cheers,
>> Anders
>
> --
> Regards,
> Atish
next prev parent reply other threads:[~2020-08-27 17:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 5:11 linux-next: Tree for Aug 27 Stephen Rothwell
2020-08-27 8:37 ` Anders Roxell
2020-08-27 17:02 ` Atish Patra
2020-08-27 17:03 ` Palmer Dabbelt [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-08-27 11:24 Stephen Rothwell
2019-08-27 9:05 Stephen Rothwell
2018-08-27 1:01 Stephen Rothwell
2018-08-27 1:00 Stephen Rothwell
2015-08-27 8:22 Stephen Rothwell
2014-08-27 6:10 Stephen Rothwell
2014-08-27 23:58 ` Guenter Roeck
2014-08-28 0:48 ` Stephen Rothwell
2014-08-28 0:56 ` Laura Abbott
2014-08-28 1:17 ` Stephen Rothwell
2013-08-27 10:30 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=mhng-16126c08-fe1d-43bf-bd48-9f1cdcdb5a57@palmerdabbelt-glaptop1 \
--to=palmerdabbelt@google.com \
--cc=Atish.Patra@wdc.com \
--cc=anders.roxell@linaro.org \
--cc=anup@brainfault.org \
--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).