From: Tzung-Bi Shih <tzungbi@kernel.org>
To: bleung@chromium.org, groeck@chromium.org
Cc: chrome-platform@lists.linux.dev, linux-kernel@vger.kernel.org,
tzungbi@kernel.org
Subject: [PATCH 0/2] platform/chrome: avoid garbage bytes in `msg->result`
Date: Wed, 20 Jul 2022 04:47:52 +0000 [thread overview]
Message-ID: <20220720044754.4026295-1-tzungbi@kernel.org> (raw)
The 1st patch merges Kunit utils and test cases. The idea is basically from
the review comment in [1].
The 2nd patch fixes that `msg->result` would be garbage bytes if the mock list
is empty. This is separated from previous series [2].
[1]: https://patchwork.kernel.org/project/chrome-platform/patch/20220718050914.2267370-2-tzungbi@kernel.org/#24944149
[2]: https://patchwork.kernel.org/project/chrome-platform/patch/20220718050914.2267370-2-tzungbi@kernel.org/
Tzung-Bi Shih (2):
platform/chrome: merge Kunit utils and test cases
platform/chrome: cros_kunit_util: add default value for `msg->result`
drivers/platform/chrome/Kconfig | 10 ++--------
drivers/platform/chrome/Makefile | 5 +++--
drivers/platform/chrome/cros_kunit_util.c | 20 +++++---------------
drivers/platform/chrome/cros_kunit_util.h | 1 +
4 files changed, 11 insertions(+), 25 deletions(-)
--
2.37.0.170.g444d1eabd0-goog
next reply other threads:[~2022-07-20 4:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 4:47 Tzung-Bi Shih [this message]
2022-07-20 4:47 ` [PATCH 1/2] platform/chrome: merge Kunit utils and test cases Tzung-Bi Shih
2022-07-20 13:01 ` Guenter Roeck
2022-07-20 4:47 ` [PATCH 2/2] platform/chrome: cros_kunit_util: add default value for `msg->result` Tzung-Bi Shih
2022-07-20 13:02 ` Guenter Roeck
2022-07-21 9:00 ` [PATCH 0/2] platform/chrome: avoid garbage bytes in `msg->result` patchwork-bot+chrome-platform
2022-07-22 0:20 ` patchwork-bot+chrome-platform
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=20220720044754.4026295-1-tzungbi@kernel.org \
--to=tzungbi@kernel.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=groeck@chromium.org \
--cc=linux-kernel@vger.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