From: Jiaxun Yang <jiaxun.yang@flygoat.com>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
Huacai Chen <chenhuacai@loongson.cn>,
Marc Zyngier <maz@kernel.org>, WANG Xuerui <git@xen0n.name>
Cc: Thomas Gleixner <tglx@linutronix.de>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org
Subject: Re: mainline build failure due to fa84f89395e0 ("irqchip/loongson-liointc: Fix build error for LoongArch")
Date: Sat, 4 Jun 2022 12:41:43 +0100 [thread overview]
Message-ID: <3ff0b2af-033f-f9d5-f6d7-c53c3e6c0858@flygoat.com> (raw)
In-Reply-To: <Yps1Jw6PJdLBya1W@debian>
在 2022/6/4 11:34, Sudip Mukherjee 写道:
> Hi All,
>
> The latest mainline kernel branch fails to build for "mips loongson2k_defconfig"
> with the error:
>
> drivers/irqchip/irq-loongson-liointc.c: In function 'liointc_chained_handle_irq':
> drivers/irqchip/irq-loongson-liointc.c:60:20: error: implicit declaration of function 'cpu_logical_map' [-Werror=implicit-function-declaration]
> 60 | int core = cpu_logical_map(smp_processor_id()) % LIOINTC_NUM_CORES;
>
>
> git bisect pointed to fa84f89395e0 ("irqchip/loongson-liointc: Fix build error for LoongArch")
>
> And, reverting it on top of mainline branch has fixed the build failure.
Thanks for the reminder.
I'll prepare a patch for it.
Thanks
- Jiaxun
>
> --
> Regards
> Sudip
next prev parent reply other threads:[~2022-06-04 11:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-04 10:34 mainline build failure due to fa84f89395e0 ("irqchip/loongson-liointc: Fix build error for LoongArch") Sudip Mukherjee
2022-06-04 11:41 ` Jiaxun Yang [this message]
2022-06-04 13:13 ` Huacai Chen
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=3ff0b2af-033f-f9d5-f6d7-c53c3e6c0858@flygoat.com \
--to=jiaxun.yang@flygoat.com \
--cc=chenhuacai@loongson.cn \
--cc=git@xen0n.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=maz@kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/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).