From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Arnd Bergmann <arnd@arndb.de>,
Naresh Kamboju <naresh.kamboju@linaro.org>,
open list <linux-kernel@vger.kernel.org>,
NXP Linux Team <linux-imx@nxp.com>,
linux-clk <linux-clk@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
lkft-triage@lists.linaro.org
Cc: Anders Roxell <anders.roxell@linaro.org>,
Abel Vesa <abelvesa@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Shawn Guo <shawnguo@kernel.org>
Subject: Re: next: arm: drivers/clk/imx/clk-imx1.c:13:10: fatal error: 'soc/imx/timer.h' file not found
Date: Fri, 23 Jun 2023 09:38:18 +0200 [thread overview]
Message-ID: <6d8590f3-7bfa-36b1-481a-b38a5779eed5@linaro.org> (raw)
In-Reply-To: <adf2429f-8d60-4cab-873a-a08530e5ce69@app.fastmail.com>
On 23/06/2023 09:22, Arnd Bergmann wrote:
> On Fri, Jun 23, 2023, at 08:51, Naresh Kamboju wrote:
>> Following build regressions noticed on Linux next-20230623.
>>
>> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>>
>>
>> Regressions found on arm:
>>
>> - build/clang-16-imx_v4_v5_defconfig
>> - build/gcc-12-imx_v4_v5_defconfig
>> - build/gcc-8-multi_v5_defconfig
>> - build/gcc-8-imx_v4_v5_defconfig
>> - build/clang-nightly-imx_v4_v5_defconfig
>
> Thanks for the report. I found the missing patch at
>
> https://lore.kernel.org/all/20230328100531.879485-2-u.kleine-koenig@pengutronix.de/
>
> and resubmitted this. It's probably best if Daniel picks
> it up into the clocksource tree, which accidentally broke the
> build by picking patch 3 of the series before patch 2.
I applied the patch and pushed the linux-next branch. That should be
fixed now.
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
prev parent reply other threads:[~2023-06-23 7:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 6:51 Naresh Kamboju
2023-06-23 7:22 ` Arnd Bergmann
2023-06-23 7:38 ` Daniel Lezcano [this message]
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=6d8590f3-7bfa-36b1-481a-b38a5779eed5@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=abelvesa@kernel.org \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=mturquette@baylibre.com \
--cc=naresh.kamboju@linaro.org \
--cc=shawnguo@kernel.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
all inboxes | Powered by JetHome®