From: patchwork-bot+chrome-platform@kernel.org
To: Stephen Boyd <swboyd@chromium.org>
Cc: bleung@chromium.org, tzungbi@kernel.org,
linux-kernel@vger.kernel.org, patches@lists.linux.dev,
chrome-platform@lists.linux.dev
Subject: Re: [PATCH 0/4] platform/chrome: Random driver cleanups
Date: Thu, 05 Oct 2023 01:56:08 +0000 [thread overview]
Message-ID: <169647096834.5479.6608928150859840412.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231003003429.1378109-1-swboyd@chromium.org>
Hello:
This series was applied to chrome-platform/linux.git (for-next)
by Tzung-Bi Shih <tzungbi@kernel.org>:
On Mon, 2 Oct 2023 17:34:24 -0700 you wrote:
> Here's some random chromeos driver cleanups that have been sitting in my
> tree. I've noticed them while browsing the code for something I'm
> working on.
>
> Stephen Boyd (4):
> platform/chrome: cros_ec_typec: Use semi-colons instead of commas
> platform/chrome: cros_ec_typec: Use dev_err_probe() more
> platform/chrome: cros_typec_vdm: Mark port_amode_ops const
> platform/chrome: cros_ec_proto: Mark outdata as const
>
> [...]
Here is the summary with links:
- [1/4] platform/chrome: cros_ec_typec: Use semi-colons instead of commas
https://git.kernel.org/chrome-platform/c/a88f6ef67957
- [2/4] platform/chrome: cros_ec_typec: Use dev_err_probe() more
https://git.kernel.org/chrome-platform/c/2b055bf8ac84
- [3/4] platform/chrome: cros_typec_vdm: Mark port_amode_ops const
https://git.kernel.org/chrome-platform/c/14e7c01cc349
- [4/4] platform/chrome: cros_ec_proto: Mark outdata as const
https://git.kernel.org/chrome-platform/c/2f3dd39e2b49
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-05 1:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 0:34 [PATCH 0/4] platform/chrome: Random driver cleanups Stephen Boyd
2023-10-03 0:34 ` [PATCH 1/4] platform/chrome: cros_ec_typec: Use semi-colons instead of commas Stephen Boyd
2023-10-03 0:34 ` [PATCH 2/4] platform/chrome: cros_ec_typec: Use dev_err_probe() more Stephen Boyd
2023-10-03 0:34 ` [PATCH 3/4] platform/chrome: cros_typec_vdm: Mark port_amode_ops const Stephen Boyd
2023-10-03 0:34 ` [PATCH 4/4] platform/chrome: cros_ec_proto: Mark outdata as const Stephen Boyd
2023-10-03 22:11 ` [PATCH 0/4] platform/chrome: Random driver cleanups Prashant Malani
2023-10-04 3:50 ` patchwork-bot+chrome-platform
2023-10-05 1:56 ` 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=169647096834.5479.6608928150859840412.git-patchwork-notify@kernel.org \
--to=patchwork-bot+chrome-platform@kernel.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@lists.linux.dev \
--cc=swboyd@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).