From: Grant Likely <grant.likely@linaro.org>
To: "Li.Xiubo@freescale.com" <Li.Xiubo@freescale.com>,
Rob Herring <robherring2@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Pantelis Antoniou <panto@antoniou-consulting.com>
Subject: RE: [PATCH] of: fix of_update_property()
Date: Tue, 04 Feb 2014 17:26:59 +0000 [thread overview]
Message-ID: <20140204172659.CEA26C4050F@trevor.secretlab.ca> (raw)
In-Reply-To: <b61be84c13ed4056a62743e16beb70f2@BY2PR03MB505.namprd03.prod.outlook.com>
On Mon, 20 Jan 2014 05:50:17 +0000, "Li.Xiubo@freescale.com" <Li.Xiubo@freescale.com> wrote:
> > Subject: Re: [PATCH] of: fix of_update_property()
> >
> > On Thu, Jan 16, 2014 at 10:46 PM, Xiubo Li <Li.Xiubo@freescale.com> wrote:
> > > The of_update_property() is intent to update a property in a node
> >
> > s/intent/indended/
> >
> > > and if the property does not exist, will add it to the node.
> > >
> > > The second search of the property is possibly won't be found, that
> > > maybe removed by other thread just before the second search begain,
> > > if so just retry it.
> >
> > How did you find this problem? Actual use or some artificial stress test?
> >
>
> Some artificial stress test at home.
Can you reproduce those tests? It would be nice to have the selftests in
the kernel so that we can regression test for problems like this.
g.
prev parent reply other threads:[~2014-02-04 17:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-17 4:46 [PATCH] of: fix of_update_property() Xiubo Li
[not found] ` < CAL_JsqJuAv8=pBuzYO5ZGzroD1kq6gjmNsTjoVyXR=vcu+-pTA@mail.gmail.com>
2014-01-17 14:49 ` Rob Herring
2014-01-17 16:42 ` Pantelis Antoniou
2014-01-20 5:50 ` Li.Xiubo
2014-02-04 17:26 ` Grant Likely [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=20140204172659.CEA26C4050F@trevor.secretlab.ca \
--to=grant.likely@linaro.org \
--cc=Li.Xiubo@freescale.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=panto@antoniou-consulting.com \
--cc=robh+dt@kernel.org \
--cc=robherring2@gmail.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 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).