From: bugzilla-daemon@bugzilla.kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 199471] [Bisected][Regression] windfarm_pm* no longer gets automatically loaded when CONFIG_I2C_POWERMAC=y is set
Date: Tue, 03 Mar 2020 12:54:12 +0000 [thread overview]
Message-ID: <bug-199471-206035-cGnlSkGqAP@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-199471-206035@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=199471
--- Comment #19 from Wolfram Sang (wsa@the-dreams.de) ---
Well, yes, the lm75 code gets loaded yet it is not clear to me if the device is
now created by DT or not. Well, we will see...
Patch sent out: http://patchwork.ozlabs.org/patch/1248349/
Let's discuss this one. The proof-of-concept here had a missing line but worked
enough.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-03-03 12:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-199471-206035@https.bugzilla.kernel.org/>
2020-02-25 15:29 ` [Bug 199471] windfarm_pm72 no longer gets automatically loaded when CONFIG_I2C_POWERMAC=y is set (regression) bugzilla-daemon
2020-03-01 19:14 ` bugzilla-daemon
2020-03-01 19:17 ` bugzilla-daemon
2020-03-01 19:46 ` [Bug 199471] [Bisected][Regression] windfarm_pm* no longer gets automatically loaded when CONFIG_I2C_POWERMAC=y is set bugzilla-daemon
2020-03-01 20:02 ` bugzilla-daemon
2020-03-01 20:10 ` bugzilla-daemon
2020-03-01 20:10 ` bugzilla-daemon
2020-03-02 13:13 ` bugzilla-daemon
2020-03-02 14:48 ` bugzilla-daemon
2020-03-02 15:39 ` bugzilla-daemon
2020-03-02 15:40 ` bugzilla-daemon
2020-03-03 12:54 ` bugzilla-daemon [this message]
2020-04-23 1:21 ` bugzilla-daemon
2020-04-23 1:36 ` bugzilla-daemon
2020-04-23 6:11 ` bugzilla-daemon
2020-04-24 3:12 ` bugzilla-daemon
2020-04-24 7:55 ` bugzilla-daemon
2020-04-24 18:33 ` bugzilla-daemon
2020-04-28 3:14 ` bugzilla-daemon
2020-04-28 3:14 ` 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-199471-206035-cGnlSkGqAP@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.