From: bugzilla-daemon@bugzilla.kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 208197] OF: /pci@f2000000/mac-io@17/gpio@50/...: could not find phandle
Date: Thu, 09 Jul 2020 17:50:56 +0000 [thread overview]
Message-ID: <bug-208197-206035-xR0UJGuLCP@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-208197-206035@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=208197
--- Comment #9 from Erhard F. (erhard_f@mailbox.org) ---
(In reply to Michael Ellerman from comment #7)
> I couldn't really make sense of your bisect log, it doesn't have any
> good/bad commits in it.
>
> Can you attach the output of "git bisect log".
Yea sorry, my fault... I thought e.g. with "git bisect bad | tee -a
~/bisect.log" bisect.log generated via tee would have the same output as with
"git bisect log" but I was wrong.
Please find the correct one attached now. I had to restart the bisect as I
already resetted the original one.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-07-09 17:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 22:02 [Bug 208197] New: OF: /pci@f2000000/mac-io@17/gpio@50/...: could not find phandle bugzilla-daemon
2020-06-15 22:03 ` [Bug 208197] " bugzilla-daemon
2020-07-05 12:50 ` bugzilla-daemon
2020-07-07 7:23 ` bugzilla-daemon
2020-07-07 12:21 ` bugzilla-daemon
2020-07-07 12:22 ` bugzilla-daemon
2020-07-07 12:30 ` bugzilla-daemon
2020-07-08 4:05 ` bugzilla-daemon
2020-07-09 17:44 ` bugzilla-daemon
2020-07-09 17:50 ` bugzilla-daemon [this message]
2022-09-12 15:22 ` bugzilla-daemon
2022-09-12 15:23 ` bugzilla-daemon
2022-09-12 15:27 ` bugzilla-daemon
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=bug-208197-206035-xR0UJGuLCP@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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).