From: patchwork-bot+chrome-platform@kernel.org
To: Prashant Malani <pmalani@chromium.org>
Cc: linux-kernel@vger.kernel.org, chrome-platform@lists.linux.dev,
bleung@chromium.org, heikki.krogerus@linux.intel.com,
groeck@chromium.org
Subject: Re: [PATCH 1/2] platform/chrome: cros_ec_typec: Rename port altmode array
Date: Mon, 18 Jul 2022 19:20:13 +0000 [thread overview]
Message-ID: <165817201341.12485.17039097052041184784.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220712210318.2671292-1-pmalani@chromium.org>
Hello:
This series was applied to chrome-platform/linux.git (for-kernelci)
by Prashant Malani <pmalani@chromium.org>:
On Tue, 12 Jul 2022 21:03:17 +0000 you wrote:
> Rename "p_altmode" to "port_altmode" which is a less ambiguous name for
> the port_altmode struct array.
>
> Signed-off-by: Prashant Malani <pmalani@chromium.org>
> ---
> drivers/platform/chrome/cros_ec_typec.c | 15 +++++++--------
> 1 file changed, 7 insertions(+), 8 deletions(-)
Here is the summary with links:
- [1/2] platform/chrome: cros_ec_typec: Rename port altmode array
https://git.kernel.org/chrome-platform/c/a47bc5a0c4c0
- [2/2] platform/chrome: cros_ec_typec: Register port altmodes
https://git.kernel.org/chrome-platform/c/1ff5d97f070c
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-07-18 19:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 21:03 [PATCH 1/2] platform/chrome: cros_ec_typec: Rename port altmode array Prashant Malani
2022-07-12 21:03 ` [PATCH 2/2] platform/chrome: cros_ec_typec: Register port altmodes Prashant Malani
2022-07-18 8:38 ` Heikki Krogerus
2022-07-18 8:37 ` [PATCH 1/2] platform/chrome: cros_ec_typec: Rename port altmode array Heikki Krogerus
2022-07-18 19:20 ` patchwork-bot+chrome-platform [this message]
2022-07-19 21:50 ` 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=165817201341.12485.17039097052041184784.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=heikki.krogerus@linux.intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox