All of lore.kernel.org
 help / color / mirror / Atom feed
From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: robh+dt@kernel.org, frowand.list@gmail.com
Cc: linux-arm-msm@vger.kernel.org, bgoswami@codeaurora.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, rohkumar@qti.qualcomm.com
Subject: Re: [PATCH] of: platform: stop accessing invalid dev in of_platform_device_destroy
Date: Sat, 2 Jun 2018 00:35:31 +0100	[thread overview]
Message-ID: <3f925507-bd67-a73d-586e-0458038a5832@linaro.org> (raw)
In-Reply-To: <20180601225822.23439-1-srinivas.kandagatla@linaro.org>



On 01/06/18 23:58, Srinivas Kandagatla wrote:
>   
> -	of_node_clear_flag(dev->of_node, OF_POPULATED);
> -	of_node_clear_flag(dev->of_node, OF_POPULATED_BUS);
This change seems to have a side effect during re-probing. I will dig in 
bit more to see how best it can be fixed.

thanks,
srini

WARNING: multiple messages have this Message-ID (diff)
From: srinivas.kandagatla@linaro.org (Srinivas Kandagatla)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] of: platform: stop accessing invalid dev in of_platform_device_destroy
Date: Sat, 2 Jun 2018 00:35:31 +0100	[thread overview]
Message-ID: <3f925507-bd67-a73d-586e-0458038a5832@linaro.org> (raw)
In-Reply-To: <20180601225822.23439-1-srinivas.kandagatla@linaro.org>



On 01/06/18 23:58, Srinivas Kandagatla wrote:
>   
> -	of_node_clear_flag(dev->of_node, OF_POPULATED);
> -	of_node_clear_flag(dev->of_node, OF_POPULATED_BUS);
This change seems to have a side effect during re-probing. I will dig in 
bit more to see how best it can be fixed.

thanks,
srini

  reply	other threads:[~2018-06-01 23:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-01 22:58 [PATCH] of: platform: stop accessing invalid dev in of_platform_device_destroy Srinivas Kandagatla
2018-06-01 22:58 ` Srinivas Kandagatla
2018-06-01 23:35 ` Srinivas Kandagatla [this message]
2018-06-01 23:35   ` Srinivas Kandagatla

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=3f925507-bd67-a73d-586e-0458038a5832@linaro.org \
    --to=srinivas.kandagatla@linaro.org \
    --cc=bgoswami@codeaurora.org \
    --cc=devicetree@vger.kernel.org \
    --cc=frowand.list@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=rohkumar@qti.qualcomm.com \
    /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.