From: Jessica Yu <jeyu@kernel.org>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Matthias Maennich <maennich@google.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 1/2] modpost: rework and consolidate logging interface
Date: Mon, 9 Mar 2020 11:58:12 +0100 [thread overview]
Message-ID: <20200309105812.GC18870@linux-8ccs.fritz.box> (raw)
In-Reply-To: <CAK7LNARpJ-FAvCUEH9rrNCiqx5LwRHmWospvRnT-ERQoEGjK-Q@mail.gmail.com>
+++ Masahiro Yamada [09/03/20 19:49 +0900]:
>On Mon, Mar 9, 2020 at 7:39 PM Jessica Yu <jeyu@kernel.org> wrote:
>>
>> Ah, sorry, I mean the kbuild 0-day bot errors. I am just realizing
>> the 0-day bot emails are not CC'd to lkml. Here is the error I got
>> from the bot:
>>
>> ---
>>
>> I love your patch! Yet something to improve:
>>
>> [auto build test ERROR on linus/master]
>> [also build test ERROR on v5.6-rc4 next-20200306]
>> [if your patch is applied to the wrong git tree, please drop us a note to help
>> improve the system. BTW, we also suggest to use '--base' option to specify the
>> base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
>>
>> url: https://github.com/0day-ci/linux/commits/Jessica-Yu/modpost-rework-and-consolidate-logging-interface/20200307-052346
>> base: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 30fe0d07fd7b27d41d9b31a224052cc4e910947a
>> config: sh-randconfig-a001-20200306 (attached as .config)
>> compiler: sh4-linux-gcc (GCC) 7.5.0
>> reproduce:
>> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
>> chmod +x ~/bin/make.cross
>> # save the attached .config to linux build tree
>> GCC_VERSION=7.5.0 make.cross ARCH=sh
>>
>> If you fix the issue, kindly add following tag
>> Reported-by: kbuild test robot <lkp@intel.com>
>>
>> All errors (new ones prefixed by >>):
>>
>> >> ERROR: modpost: "adc_single" [arch/sh/boards/mach-hp6xx/hp6xx_apm.ko] undefined!
>
>
>Indeed, this one is odd.
>I have no idea...
I've pushed the patches to a branch to let the kbuild bot run through its
build tests again, and if I have extra time today I will try to
reproduce this and let you know the results.
Thanks,
Jessica
next prev parent reply other threads:[~2020-03-09 10:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 16:02 [PATCH v3 1/2] modpost: rework and consolidate logging interface Jessica Yu
2020-03-06 16:02 ` [PATCH v3 2/2] modpost: return error if module is missing ns imports and MODULE_ALLOW_MISSING_NAMESPACE_IMPORTS=n Jessica Yu
2020-03-09 0:40 ` [PATCH v3 1/2] modpost: rework and consolidate logging interface Masahiro Yamada
2020-03-09 9:59 ` Jessica Yu
2020-03-09 10:20 ` Masahiro Yamada
2020-03-09 10:39 ` Jessica Yu
2020-03-09 10:49 ` Masahiro Yamada
2020-03-09 10:58 ` Jessica Yu [this message]
2020-03-09 11:03 ` Masahiro Yamada
2020-03-10 11:32 ` Jessica Yu
2020-03-10 15:55 ` [LKP] " Philip Li
2020-03-11 1:00 ` Masahiro Yamada
2020-03-11 12:26 ` Philip Li
2020-03-12 0:50 ` Rong Chen
2020-03-11 0:56 ` Masahiro Yamada
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=20200309105812.GC18870@linux-8ccs.fritz.box \
--to=jeyu@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maennich@google.com \
--cc=masahiroy@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