From: bugzilla-daemon@bugzilla.kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 201723] THERM_WINDTUNNEL not working any longer in kernel 4.19.x (PowerMac G4 MDD)
Date: Thu, 17 Oct 2019 22:49:00 +0000 [thread overview]
Message-ID: <bug-201723-206035-Uz3QyqaxJB@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-201723-206035@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=201723
--- Comment #4 from Erhard F. (erhard_f@mailbox.org) ---
Created attachment 285535
--> https://bugzilla.kernel.org/attachment.cgi?id=285535&action=edit
bisect.log
Final bisect commit.
It's not a bug, it's a feature. :(
# git bisect bad | tee -a ~/bisect.log
3e7bed52719de4b5b5fb900869e293eae0bc3f3e is the first bad commit
commit 3e7bed52719de4b5b5fb900869e293eae0bc3f3e
Author: Wolfram Sang <wsa@the-dreams.de>
Date: Tue Aug 21 17:02:39 2018 +0200
macintosh: therm_windtunnel: drop using attach_adapter
As we now have deferred probing, we can use a custom mechanism and
finally get rid of the legacy interface from the i2c core.
Signed-off-by: Wolfram Sang <wsa@the-dreams.de>
Acked-by: Michael Ellerman <mpe@ellerman.id.au>
:040000 040000 04029fe24bce33dd0b815fa961cfa847a2abce77
2dc14e16e628b7e2fa4b65bfd6544c9c5e165a9a M drivers
--
You are receiving this mail because:
You are watching the assignee of the bug.
next parent reply other threads:[~2019-10-17 22:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-201723-206035@https.bugzilla.kernel.org/>
2019-10-17 22:49 ` bugzilla-daemon [this message]
2020-02-11 12:13 ` [Bug 201723] [Bisected][Regression] THERM_WINDTUNNEL not working any longer in kernel 4.19.x (PowerMac G4 MDD) bugzilla-daemon
2020-02-25 14:59 ` bugzilla-daemon
2020-03-02 13:16 ` 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-201723-206035-Uz3QyqaxJB@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 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.