From: patchwork-bot+chrome-platform@kernel.org
To: Prashant Malani <pmalani@chromium.org>
Cc: linux-kernel@vger.kernel.org, bleung@chromium.org,
chrome-platform@lists.linux.dev, groeck@chromium.org
Subject: Re: [PATCH v2 0/4] platform/chrome: cros_ec_typec: Reorganize mux configuration
Date: Tue, 15 Feb 2022 20:00:10 +0000 [thread overview]
Message-ID: <164495521075.19688.3105207399888394248.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220208184721.1697194-1-pmalani@chromium.org>
Hello:
This series was applied to chrome-platform/linux.git (for-kernelci)
by Prashant Malani <pmalani@chromium.org>:
On Tue, 8 Feb 2022 18:47:16 +0000 you wrote:
> This is a short series that reorganizes when mux configuration occurs
> during Type C port updates. The first 2 patches are minor refactors
> which move some of the mux update logic to within
> cros_typec_configure_mux(). The third patch moves
> cros_typec_configure_mux() itself to be earlier in
> cros_typec_port_update().
>
> [...]
Here is the summary with links:
- [v2,1/4] platform/chrome: cros_ec_typec: Move mux flag checks
https://git.kernel.org/chrome-platform/c/53a0023c6450
- [v2,2/4] platform/chrome: cros_ec_typec: Get mux state inside configure_mux
https://git.kernel.org/chrome-platform/c/0d8495dc0321
- [v2,3/4] platform/chrome: cros_ec_typec: Configure muxes at start of port update
https://git.kernel.org/chrome-platform/c/af34f115b3b7
- [v2,4/4] platform/chrome: cros_ec_typec: Update mux flags during partner removal
https://git.kernel.org/chrome-platform/c/b579f139e470
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-02-15 20:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 18:47 [PATCH v2 0/4] platform/chrome: cros_ec_typec: Reorganize mux configuration Prashant Malani
2022-02-08 18:47 ` [PATCH v2 1/4] platform/chrome: cros_ec_typec: Move mux flag checks Prashant Malani
2022-02-09 3:32 ` Tzung-Bi Shih
2022-02-08 18:47 ` [PATCH v2 2/4] platform/chrome: cros_ec_typec: Get mux state inside configure_mux Prashant Malani
2022-02-09 3:32 ` Tzung-Bi Shih
2022-02-08 18:47 ` [PATCH v2 3/4] platform/chrome: cros_ec_typec: Configure muxes at start of port update Prashant Malani
2022-02-15 0:27 ` Benson Leung
2022-02-08 18:47 ` [PATCH v2 4/4] platform/chrome: cros_ec_typec: Update mux flags during partner removal Prashant Malani
2022-02-09 3:32 ` Tzung-Bi Shih
2022-02-15 20:00 ` patchwork-bot+chrome-platform [this message]
2022-02-16 22:00 ` [PATCH v2 0/4] platform/chrome: cros_ec_typec: Reorganize mux configuration 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=164495521075.19688.3105207399888394248.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=pmalani@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.