From: "Chen, Rong A" <rong.a.chen@intel.com>
To: Arnd Bergmann <arnd@arndb.de>, kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Greg Ungerer <gerg@linux-m68k.org>,
Daniel Palmer <daniel@0x0f.com>
Subject: Re: [kbuild-all] Re: time.c:undefined reference to `mach_get_rtc_pll'
Date: Fri, 6 May 2022 16:16:06 +0800 [thread overview]
Message-ID: <45842084-938c-1e86-8b40-e883c9ae40bb@intel.com> (raw)
In-Reply-To: <CAK8P3a3F3Z1NyhVcK6wN+b6Es3gqiYGee8a+pAPsaer4hhHDbQ@mail.gmail.com>
On 5/4/2022 5:25 PM, Arnd Bergmann wrote:
> On Wed, May 4, 2022 at 11:14 AM kernel test robot <lkp@intel.com> wrote:
>>
>> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>> head: 107c948d1d3e61d10aee9d0f7c3d81bbee9842af
>> commit: 8b22820efb35f93d98638563b0a8f4094e8ee399 m68k: m68328: remove duplicate code
>>
>> If you fix the issue, kindly add following tag as appropriate
>> Reported-by: kernel test robot <lkp@intel.com>
>>
>> All errors (new ones prefixed by >>):
>>
>> m68k-linux-ld: arch/m68k/kernel/time.o: in function `rtc_ioctl':
>>>> time.c:(.text+0x82): undefined reference to `mach_get_rtc_pll'
>> m68k-linux-ld: time.c:(.text+0xbc): undefined reference to `mach_set_rtc_pll'
>> m68k-linux-ld: time.c:(.text+0xf4): undefined reference to `mach_set_rtc_pll'
>>
>
> I think this is just another build failure that was hidden before my patch,
> not caused by my patch.
>
> Arnd
Hi Arnd,
Sorry for the inconvenience, we have added it to the ignore list.
Best Regards,
Rong Chen
prev parent reply other threads:[~2022-05-06 8:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 9:14 kernel test robot
2022-05-04 9:25 ` Arnd Bergmann
2022-05-04 13:33 ` Geert Uytterhoeven
2022-05-06 7:21 ` Arnd Bergmann
2022-05-06 7:23 ` Geert Uytterhoeven
2022-05-12 4:01 ` Randy Dunlap
2022-05-06 8:16 ` Chen, Rong A [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=45842084-938c-1e86-8b40-e883c9ae40bb@intel.com \
--to=rong.a.chen@intel.com \
--cc=arnd@arndb.de \
--cc=daniel@0x0f.com \
--cc=gerg@linux-m68k.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
/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®