From: Grant Likely <grant.likely@linaro.org>
To: Rob Herring <robherring2@gmail.com>,
Wang Long <long.wanglong@huawei.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Gaurav Minocha <gaurav.minocha.os@gmail.com>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
peifeiyue@huawei.com
Subject: Re: [PATCH v2 1/2] Documentation: update the of_selftest.txt
Date: Fri, 27 Mar 2015 18:37:57 -0700 [thread overview]
Message-ID: <20150328013757.EAFE5C40A4A@trevor.secretlab.ca> (raw)
In-Reply-To: <CAL_JsqJiWhXQqGCik9tDqyaXEqU8+gEdw=FBVL_Fddbk_SjfwQ@mail.gmail.com>
On Tue, 10 Mar 2015 09:50:58 -0500
, Rob Herring <robherring2@gmail.com>
wrote:
> On Tue, Mar 10, 2015 at 9:44 AM, Rob Herring <robherring2@gmail.com> wrote:
> > On Sun, Mar 8, 2015 at 9:35 PM, Wang Long <long.wanglong@huawei.com> wrote:
> >> Since the directory "drivers/of/testcase-data" is renamed
> >> to "drivers/of/unittest-data". so we should update the path
> >> in the of_selftest.txt.
>
> [...]
>
> >> -Before executing OF selftest, it is required to attach the test data to
> >> +Before executing OF unittest, it is required to attach the test data to
> >> machine's device tree (if present). So, when selftest_data_add() is called,
> >
> > This one too.
>
> Or not. The functions are all still "selftest". Not sure why Grant
> left all those...
Because it was churn, and there were patches in-flight that would be
affected. They can be changed now.
g.
prev parent reply other threads:[~2015-03-28 12:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-09 2:35 Wang Long
2015-03-09 2:35 ` [PATCH v2 2/2] Documentation: rename of_selftest.txt to of_unittest.txt Wang Long
2015-03-10 14:44 ` [PATCH v2 1/2] Documentation: update the of_selftest.txt Rob Herring
2015-03-10 14:50 ` Rob Herring
[not found] ` <CA+rpMb+xL4g5bzGQhUe7kFkCmpH3VwGXsVP3zypW1w6366gAkw@mail.gmail.com>
2015-03-11 3:07 ` long.wanglong
2015-03-28 1:37 ` 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=20150328013757.EAFE5C40A4A@trevor.secretlab.ca \
--to=grant.likely@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=gaurav.minocha.os@gmail.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=long.wanglong@huawei.com \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=peifeiyue@huawei.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
all inboxes | Powered by JetHome®