From: Brendan Higgins <brendanhiggins@google.com>
To: robh+dt@kernel.org, frowand.list@gmail.com, mcgrof@kernel.org
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Brendan Higgins <brendanhiggins@google.com>
Subject: [PATCH v1 0/1] of: unittest: unflatten device tree on UML when testing
Date: Tue, 12 Feb 2019 10:53:04 -0800 [thread overview]
Message-ID: <20190212185305.112847-1-brendanhiggins@google.com> (raw)
This patch set unflattens device trees when running DT's unittest. It is
a follow up to
https://www.spinics.net/lists/linux-kselftest/msg05454.html part of the
KUnit RFC v3 thread
(https://www.spinics.net/lists/linux-kselftest/msg05431.html). Rob asked
me to submit this patch separately along with some modifications.
--
2.20.1.791.gb4d0f1c61a-goog
next reply other threads:[~2019-02-12 18:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 18:53 Brendan Higgins [this message]
2019-02-12 18:53 ` [PATCH v1 1/1] of: unittest: unflatten device tree on UML when testing Brendan Higgins
2019-02-13 19:12 ` Rob Herring
2019-02-15 0:10 ` Frank Rowand
2019-02-15 1:26 ` Brendan Higgins
2019-02-15 2:48 ` Frank Rowand
2019-02-15 9:49 ` Brendan Higgins
2019-02-15 19:44 ` Rob Herring
2019-02-15 23:06 ` Frank Rowand
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=20190212185305.112847-1-brendanhiggins@google.com \
--to=brendanhiggins@google.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=robh+dt@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).