From: patchwork-bot+chrome-platform@kernel.org
To: Tzung-Bi Shih <tzungbi@kernel.org>
Cc: bleung@chromium.org, groeck@chromium.org,
chrome-platform@lists.linux.dev
Subject: Re: [PATCH] platform/chrome: kunit: make EC protocol tests independent
Date: Wed, 11 Oct 2023 02:20:22 +0000 [thread overview]
Message-ID: <169699082237.9318.7672925341638531288.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231003080515.4011374-1-tzungbi@kernel.org>
Hello:
This patch was applied to chrome-platform/linux.git (for-next)
by Tzung-Bi Shih <tzungbi@kernel.org>:
On Tue, 3 Oct 2023 08:05:15 +0000 you wrote:
> Remove CONFIG_CROS_KUNIT and common code concept for ChromeOS Kunit but
> make it bundle to ChromeOS EC protocol tests.
>
> Signed-off-by: Tzung-Bi Shih <tzungbi@kernel.org>
> ---
> drivers/platform/chrome/Kconfig | 6 +++---
> drivers/platform/chrome/Makefile | 5 ++---
> drivers/platform/chrome/cros_ec_proto_test.c | 2 +-
> .../chrome/{cros_kunit_util.c => cros_ec_proto_test_util.c} | 4 +---
> .../chrome/{cros_kunit_util.h => cros_ec_proto_test_util.h} | 0
> 5 files changed, 7 insertions(+), 10 deletions(-)
> rename drivers/platform/chrome/{cros_kunit_util.c => cros_ec_proto_test_util.c} (98%)
> rename drivers/platform/chrome/{cros_kunit_util.h => cros_ec_proto_test_util.h} (100%)
Here is the summary with links:
- platform/chrome: kunit: make EC protocol tests independent
https://git.kernel.org/chrome-platform/c/466f70fb1b10
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-10-11 2:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 8:05 [PATCH] platform/chrome: kunit: make EC protocol tests independent Tzung-Bi Shih
2023-10-05 2:16 ` Guenter Roeck
2023-10-05 10:20 ` patchwork-bot+chrome-platform
2023-10-11 2:20 ` patchwork-bot+chrome-platform [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=169699082237.9318.7672925341638531288.git-patchwork-notify@kernel.org \
--to=patchwork-bot+chrome-platform@kernel.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=groeck@chromium.org \
--cc=tzungbi@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