Chrome platform driver development
 help / color / mirror / Atom feed
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: cros_ec_proto: update Kunit test for get_next_data_v3
Date: Wed, 12 Jun 2024 02:30:30 +0000	[thread overview]
Message-ID: <171815943071.29023.7456200928151542183.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240611033113.4154548-1-tzungbi@kernel.org>

Hello:

This patch was applied to chrome-platform/linux.git (for-kernelci)
by Tzung-Bi Shih <tzungbi@kernel.org>:

On Tue, 11 Jun 2024 03:31:13 +0000 you wrote:
> Since commit 106d67398233 ("platform/chrome: cros_ec_proto: Upgrade
> get_next_event to v3"), (struct cros_ec_device *)->event_data becomes
> struct ec_response_get_next_event_v3.
> 
> Update the Kunit test for fixing the following error:
> > Expected mock->msg.insize == sizeof(union ec_response_get_next_data_v1), but
> >     mock->msg.insize == 18 (0x12)
> >     sizeof(union ec_response_get_next_data_v1) == 16 (0x10)
> 
> [...]

Here is the summary with links:
  - platform/chrome: cros_ec_proto: update Kunit test for get_next_data_v3
    https://git.kernel.org/chrome-platform/c/41f1242f6249

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  parent reply	other threads:[~2024-06-12  2:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-11  3:31 [PATCH] platform/chrome: cros_ec_proto: update Kunit test for get_next_data_v3 Tzung-Bi Shih
2024-06-11 16:39 ` Guenter Roeck
2024-06-12  2:30 ` patchwork-bot+chrome-platform [this message]
2024-06-12  2:30 ` 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=171815943071.29023.7456200928151542183.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