From: Krzysztof Kozlowski <krzk@kernel.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: Thierry Reding <treding@nvidia.com>,
kernel test robot <lkp@intel.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Dmitry Osipenko <digetx@gmail.com>,
"kbuild-all@lists.01.org" <kbuild-all@lists.01.org>,
"clang-built-linux@googlegroups.com"
<clang-built-linux@googlegroups.com>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [linux-next:master 5946/11253] ld.lld: error: undefined symbol: reset_controller_register
Date: Fri, 18 Jun 2021 17:05:30 +0200 [thread overview]
Message-ID: <6188a28e-8184-fbb0-6e49-1c674dbf84a7@kernel.org> (raw)
In-Reply-To: <YMy1DpeyrYm/pwYF@casper.infradead.org>
On 18/06/2021 17:00, Matthew Wilcox wrote:
> On Fri, Jun 18, 2021 at 04:55:23PM +0200, Krzysztof Kozlowski wrote:
>> These are randconfigs, so I don't think Linus will hit them when
>> merging. Therefore assuming the reset-stubs are applied (and tree is in
>> next), we should be fine, shouldn't we?
>
> It's a bisection hazard. Please fix it before the merge. This is
> exactly the kind of thing that linux-next is designed to detect.
Still hazard for a compile testing configuration, not a real bisection
for troubleshooting bugs. You cannot hit the bug in any real case (so
!COMPILE_TEST).
The only way to reduce the bisection hazard is me to take reset stubs.
Best regards,
Krzysztof
next prev parent reply other threads:[~2021-06-18 15:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-18 14:21 [linux-next:master 5946/11253] ld.lld: error: undefined symbol: reset_controller_register kernel test robot
2021-06-18 14:52 ` Thierry Reding
2021-06-18 14:55 ` Krzysztof Kozlowski
2021-06-18 15:00 ` Matthew Wilcox
2021-06-18 15:05 ` Krzysztof Kozlowski [this message]
2021-06-18 15:11 ` Thierry Reding
2021-06-18 15:14 ` Krzysztof Kozlowski
2021-06-18 15:53 ` Philipp Zabel
2021-06-21 9:27 ` Krzysztof Kozlowski
2021-06-21 10:51 ` Philipp Zabel
2021-06-18 15:20 ` Philipp Zabel
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=6188a28e-8184-fbb0-6e49-1c674dbf84a7@kernel.org \
--to=krzk@kernel.org \
--cc=clang-built-linux@googlegroups.com \
--cc=digetx@gmail.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=p.zabel@pengutronix.de \
--cc=treding@nvidia.com \
--cc=willy@infradead.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).