From: Philipp Zabel <p.zabel@pengutronix.de>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Thierry Reding <treding@nvidia.com>,
kernel test robot <lkp@intel.com>,
Olof Johansson <olof@lixom.net>
Cc: 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: Mon, 21 Jun 2021 12:51:22 +0200 [thread overview]
Message-ID: <68a0278fac134b81ecc48582fd386206dd3af244.camel@pengutronix.de> (raw)
In-Reply-To: <a9a17943-e672-2475-5e30-244283986a7c@kernel.org>
On Mon, 2021-06-21 at 11:27 +0200, Krzysztof Kozlowski wrote:
[...]
> It won't change the bisectability, just the scope will be few commits
> narrower. The damage is unfortunately done.
Oh right, so the only way to fix this would have been to rebase your
branch on top of mine before the pull request.
I'll try to be more careful about spotting and pointing out such
dependencies when picking patches out of series. If I still miss them
and pick up a patch that you think should be merged together with the
rest of the series, don't hesitate to ask me to drop it from my tree.
More often than not, I have no conflicting patches pending.
regards
Philipp
WARNING: multiple messages have this Message-ID (diff)
From: Philipp Zabel <p.zabel@pengutronix.de>
To: kbuild-all@lists.01.org
Subject: Re: [linux-next:master 5946/11253] ld.lld: error: undefined symbol: reset_controller_register
Date: Mon, 21 Jun 2021 12:51:22 +0200 [thread overview]
Message-ID: <68a0278fac134b81ecc48582fd386206dd3af244.camel@pengutronix.de> (raw)
In-Reply-To: <a9a17943-e672-2475-5e30-244283986a7c@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 673 bytes --]
On Mon, 2021-06-21 at 11:27 +0200, Krzysztof Kozlowski wrote:
[...]
> It won't change the bisectability, just the scope will be few commits
> narrower. The damage is unfortunately done.
Oh right, so the only way to fix this would have been to rebase your
branch on top of mine before the pull request.
I'll try to be more careful about spotting and pointing out such
dependencies when picking patches out of series. If I still miss them
and pick up a patch that you think should be merged together with the
rest of the series, don't hesitate to ask me to drop it from my tree.
More often than not, I have no conflicting patches pending.
regards
Philipp
next prev parent reply other threads:[~2021-06-21 10:51 UTC|newest]
Thread overview: 22+ 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:21 ` kernel test robot
2021-06-18 14:52 ` Thierry Reding
2021-06-18 14:52 ` Thierry Reding
2021-06-18 14:55 ` Krzysztof Kozlowski
2021-06-18 14:55 ` Krzysztof Kozlowski
2021-06-18 15:00 ` Matthew Wilcox
2021-06-18 15:00 ` Matthew Wilcox
2021-06-18 15:05 ` Krzysztof Kozlowski
2021-06-18 15:05 ` Krzysztof Kozlowski
2021-06-18 15:11 ` Thierry Reding
2021-06-18 15:11 ` Thierry Reding
2021-06-18 15:14 ` Krzysztof Kozlowski
2021-06-18 15:14 ` Krzysztof Kozlowski
2021-06-18 15:53 ` Philipp Zabel
2021-06-18 15:53 ` Philipp Zabel
2021-06-21 9:27 ` Krzysztof Kozlowski
2021-06-21 9:27 ` Krzysztof Kozlowski
2021-06-21 10:51 ` Philipp Zabel [this message]
2021-06-21 10:51 ` Philipp Zabel
2021-06-18 15:20 ` 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=68a0278fac134b81ecc48582fd386206dd3af244.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=clang-built-linux@googlegroups.com \
--cc=digetx@gmail.com \
--cc=kbuild-all@lists.01.org \
--cc=krzk@kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=olof@lixom.net \
--cc=treding@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.