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, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/7] platform/chrome: get rid of BUG_ON()
Date: Mon, 16 May 2022 02:10:14 +0000 [thread overview]
Message-ID: <165266701479.14602.4419757446992775203.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220513044143.1045728-1-tzungbi@kernel.org>
Hello:
This series was applied to chrome-platform/linux.git (for-kernelci)
by Tzung-Bi Shih <tzungbi@kernel.org>:
On Fri, 13 May 2022 12:41:36 +0800 you wrote:
> The series gets rid of BUG_ON()s in drivers/platform/chrome/. Most of them
> can be replaced by returning proper return code.
>
> The 2nd patch makes callers of cros_ec_prepare_tx() to take care of the
> return code.
>
> The 3rd patch turns cros_ec_prepare_tx() to return error code if any.
>
> [...]
Here is the summary with links:
- [v2,1/7] platform/chrome: cros_ec_proto: drop unneeded BUG_ON() in prepare_packet()
https://git.kernel.org/chrome-platform/c/42701e7c0cd2
- [v2,2/7] platform/chrome: correct cros_ec_prepare_tx() usage
https://git.kernel.org/chrome-platform/c/71d3ae7fb640
- [v2,3/7] platform/chrome: cros_ec_proto: drop BUG_ON() in cros_ec_prepare_tx()
https://git.kernel.org/chrome-platform/c/c2dcb1b06053
- [v2,4/7] platform/chrome: cros_ec_proto: drop BUG_ON() in cros_ec_get_host_event()
https://git.kernel.org/chrome-platform/c/20a264c97bc8
- [v2,5/7] platform/chrome: cros_ec_i2c: drop BUG_ON() in cros_ec_pkt_xfer_i2c()
https://git.kernel.org/chrome-platform/c/8bff946c4199
- [v2,6/7] platform/chrome: cros_ec_spi: drop unneeded BUG_ON()
https://git.kernel.org/chrome-platform/c/ddec8e9e90ce
- [v2,7/7] platform/chrome: cros_ec_spi: drop BUG_ON() if `din` isn't large enough
https://git.kernel.org/chrome-platform/c/bbd43a37ec7a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-05-16 2:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 4:41 [PATCH v2 0/7] platform/chrome: get rid of BUG_ON() Tzung-Bi Shih
2022-05-13 4:41 ` [PATCH v2 1/7] platform/chrome: cros_ec_proto: drop unneeded BUG_ON() in prepare_packet() Tzung-Bi Shih
2022-05-13 4:41 ` [PATCH v2 2/7] platform/chrome: correct cros_ec_prepare_tx() usage Tzung-Bi Shih
2022-05-13 4:41 ` [PATCH v2 3/7] platform/chrome: cros_ec_proto: drop BUG_ON() in cros_ec_prepare_tx() Tzung-Bi Shih
2022-05-13 4:41 ` [PATCH v2 4/7] platform/chrome: cros_ec_proto: drop BUG_ON() in cros_ec_get_host_event() Tzung-Bi Shih
2022-05-13 4:41 ` [PATCH v2 5/7] platform/chrome: cros_ec_i2c: drop BUG_ON() in cros_ec_pkt_xfer_i2c() Tzung-Bi Shih
2022-05-13 4:41 ` [PATCH v2 6/7] platform/chrome: cros_ec_spi: drop unneeded BUG_ON() Tzung-Bi Shih
2022-05-13 13:19 ` Guenter Roeck
2022-05-13 4:41 ` [PATCH v2 7/7] platform/chrome: cros_ec_spi: drop BUG_ON() if `din` isn't large enough Tzung-Bi Shih
2022-05-13 13:20 ` Guenter Roeck
2022-05-16 2:10 ` patchwork-bot+chrome-platform [this message]
2022-05-18 5:20 ` [PATCH v2 0/7] platform/chrome: get rid of BUG_ON() 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=165266701479.14602.4419757446992775203.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=linux-kernel@vger.kernel.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