From: Chanwoo Choi <cw00.choi@samsung.com>
To: Brian Norris <briannorris@chromium.org>
Cc: kernel test robot <lkp@intel.com>,
llvm@lists.linux.dev, kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Douglas Anderson <dianders@chromium.org>
Subject: Re: [linux-next:master 9269/14079] ld.lld: error: undefined symbol: rockchip_pmu_block
Date: Wed, 25 May 2022 12:09:22 +0900 [thread overview]
Message-ID: <39b07203-111f-0fb9-7c9a-120a067ca1a6@samsung.com> (raw)
In-Reply-To: <CA+ASDXNQ=ycB9v=FpNup2SM2Qd+W32M5c7vsh=jXG0qB_d_35w@mail.gmail.com>
Hi Brian,
On 5/25/22 10:16 AM, Brian Norris wrote:
> Hi Chanwoo,
>
> On Tue, May 24, 2022 at 6:04 PM Chanwoo Choi <cw00.choi@samsung.com> wrote:
>> How can fix this build issue?
>> Should I add the ARCH_ROCKCHIP dependency to rk3399_dmc.c?
>
> No. As noted below by the robot, the issue is already fixed in -next.
> I noted as much already on the earlier reports:
> https://lore.kernel.org/all/CA+ASDXO1JDKf-vBB0gWdYKD9vMMoMXYRL2E42HJtnbOvMP7jPA@mail.gmail.com/
>
> Unfortunately, the two changes were picked up to different trees at
> different times, so it's not bisectable. (It's not that severe IMO,
> since the build failure can only occur for COMPILE_TEST=y.)
>
>> On 5/24/22 8:49 PM, kernel test robot wrote:
>>> Note: the linux-next/master HEAD 09ce5091ff971cdbfd67ad84dc561ea27f10d67a builds fine.
>>> It may have been fixed somewhere.
>
OK. Thanks for the reply.
--
Best Regards,
Chanwoo Choi
Samsung Electronics
prev parent reply other threads:[~2022-05-25 3:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220524114954epcas1p416e486dce031a941263b13120e717d72@epcas1p4.samsung.com>
2022-05-24 11:49 ` kernel test robot
2022-05-25 1:04 ` Chanwoo Choi
2022-05-25 1:16 ` Brian Norris
2022-05-25 3:09 ` Chanwoo Choi [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=39b07203-111f-0fb9-7c9a-120a067ca1a6@samsung.com \
--to=cw00.choi@samsung.com \
--cc=briannorris@chromium.org \
--cc=dianders@chromium.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
/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