public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Kevin Hao <haokexin@gmail.com>
Cc: linux-i2c@vger.kernel.org
Subject: Re: [PATCH] i2c: dev: Fix the race between the release of i2c_dev and cdev
Date: Sat, 21 Mar 2020 10:47:20 +0100	[thread overview]
Message-ID: <20200321094719.GA1856@ninjato> (raw)
In-Reply-To: <20200321040517.GA1315042@pek-khao-d2.corp.ad.wrs.com>

[-- Attachment #1: Type: text/plain, Size: 804 bytes --]


> > I didn't get this trace on my ARM32 board (Renesas Lager). Anything more
> > I need to do besides activating those options and using i2c-dev?
> 
> CONFIG_DEBUG_OBJECTS_FREE is also needed. I got this bug warning when running
> the OF unittest, so you may need to enable the following kernel options if you
> also want to reproduce this by using that.
>     CONFIG_OF_UNITTEST
>     CONFIG_OF_OVERLAY

Great! With all these config switches I could reproduce the error and
see it is gone with your patch (still two backtraces left, but this is
something else). Thanks for the heads up!

> Yes, there is a conflict with the latest kernel. Do I need to resend a new
> version?

Nope, it was trivial and I fixed it anyhow for my testing.

Thanks for doing it and for your patience!


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-03-21  9:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20191011150014.28177-1-haokexin@gmail.com>
     [not found] ` <20191125193204.GA14257@kunai>
2020-03-16  4:54   ` [PATCH] i2c: dev: Fix the race between the release of i2c_dev and cdev Kevin Hao
2020-03-20 18:01 ` Wolfram Sang
2020-03-21  4:05   ` Kevin Hao
2020-03-21  9:47     ` Wolfram Sang [this message]
2020-03-21  9:47 ` Wolfram Sang

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=20200321094719.GA1856@ninjato \
    --to=wsa@the-dreams.de \
    --cc=haokexin@gmail.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