From: frowand.list@gmail.com
To: Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] of: unittest: minor cleanups
Date: Thu, 24 Jan 2019 15:22:12 -0800 [thread overview]
Message-ID: <1548372134-15729-1-git-send-email-frowand.list@gmail.com> (raw)
From: Frank Rowand <frank.rowand@sony.com>
1) Suppress expected error message when adding unittest data to livetree.
2) While writing patch 1, noted a misleading function name. Add comment
to the function header warning about possible unexpected results.
Frank Rowand (2):
of: unittest: remove report of expected error
of: unittest: add caution to function header comment
drivers/of/unittest.c | 11 +++++++++--
1 file changed, 9 insertions(+), 2 deletions(-)
--
Frank Rowand <frank.rowand@sony.com>
next reply other threads:[~2019-01-24 23:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-24 23:22 frowand.list [this message]
2019-01-24 23:22 ` [PATCH 1/2] of: unittest: remove report of expected error frowand.list
2019-01-24 23:22 ` [PATCH 2/2] of: unittest: add caution to function header comment frowand.list
2019-02-13 19:09 ` [PATCH 0/2] of: unittest: minor cleanups Rob Herring
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=1548372134-15729-1-git-send-email-frowand.list@gmail.com \
--to=frowand.list@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.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).