From: patchwork-bot+chrome-platform@kernel.org
To: Akihiko Odaki <akihiko.odaki@gmail.com>
Cc: linux-kernel@vger.kernel.org, chrome-platform@lists.linux.dev,
pmalani@chromium.org, bleung@chromium.org, groeck@chromium.org
Subject: Re: [PATCH] platform/chrome: cros_ec_typec: Check for EC driver
Date: Tue, 10 May 2022 23:00:13 +0000 [thread overview]
Message-ID: <165222361336.23551.5993886315130688709.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220404041101.6276-1-akihiko.odaki@gmail.com>
Hello:
This patch was applied to chrome-platform/linux.git (for-kernelci)
by Prashant Malani <pmalani@chromium.org>:
On Mon, 4 Apr 2022 13:11:01 +0900 you wrote:
> The EC driver may not be initialized when cros_typec_probe is called,
> particulary when CONFIG_CROS_EC_CHARDEV=m.
>
> Signed-off-by: Akihiko Odaki <akihiko.odaki@gmail.com>
> ---
> drivers/platform/chrome/cros_ec_typec.c | 3 +++
> 1 file changed, 3 insertions(+)
Here is the summary with links:
- platform/chrome: cros_ec_typec: Check for EC driver
https://git.kernel.org/chrome-platform/c/7464ff8bf2d7
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-10 23:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 4:11 [PATCH] platform/chrome: cros_ec_typec: Check for EC driver Akihiko Odaki
2022-04-04 4:11 ` Akihiko Odaki
2022-04-05 1:57 ` Guenter Roeck
2022-04-05 5:43 ` Akihiko Odaki
2022-04-06 21:16 ` Prashant Malani
2022-04-06 21:32 ` Guenter Roeck
2022-04-07 1:16 ` Akihiko Odaki
2022-04-07 16:28 ` Guenter Roeck
2022-04-07 17:03 ` Akihiko Odaki
2022-04-07 17:09 ` Benson Leung
2022-04-07 17:23 ` Akihiko Odaki
2022-04-07 18:51 ` Guenter Roeck
2022-04-20 10:50 ` patchwork-bot+chrome-platform
2022-05-10 23:00 ` patchwork-bot+chrome-platform [this message]
2022-05-12 17:20 ` 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=165222361336.23551.5993886315130688709.git-patchwork-notify@kernel.org \
--to=patchwork-bot+chrome-platform@kernel.org \
--cc=akihiko.odaki@gmail.com \
--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.