From: Jean Delvare <jdelvare@suse.de>
To: Johnny Bieren <jbieren@redhat.com>
Cc: linux-i2c@vger.kernel.org
Subject: Re: amd756 driver error introduced with kernel-4.9.0-0.rc1.git0.2.fc26
Date: Wed, 9 Nov 2016 14:54:12 +0100 [thread overview]
Message-ID: <20161109145412.151c9ffc@endymion> (raw)
In-Reply-To: <58221469.50005@redhat.com>
On Tue, 8 Nov 2016 13:07:37 -0500, Johnny Bieren wrote:
> No, that option is not enabled.
>
> cat /boot/config-4.9.0-0.rc1.git0.2.fc26.x86_64 | grep DEBUG_TEST
> # CONFIG_DEBUG_TEST_DRIVER_REMOVE is not set
Then I don't know. I can't see how the only recent change to the
i2c-amd756 driver (ea734404f3daf1f6b5103171d848c9d4641fd96b) could
cause this. The warning comes from:
WARN_ON(!list_empty(&dev->devres_head));
which was added a decade ago so nothing new here.
I'm out of ideas. The only way to move forward is to bisect it to find
out the exact commit which triggered the warning.
--
Jean Delvare
SUSE L3 Support
prev parent reply other threads:[~2016-11-09 13:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-08 12:50 amd756 driver error introduced with kernel-4.9.0-0.rc1.git0.2.fc26 Johnny Bieren
2016-11-08 13:58 ` Jean Delvare
2016-11-08 18:07 ` Johnny Bieren
2016-11-09 13:54 ` Jean Delvare [this message]
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=20161109145412.151c9ffc@endymion \
--to=jdelvare@suse.de \
--cc=jbieren@redhat.com \
--cc=linux-i2c@vger.kernel.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).