From: patchwork-bot+chrome-platform@kernel.org
To: Victor Ding <victording@chromium.org>
Cc: linux-kernel@vger.kernel.org, chrome-platform@lists.linux.dev,
heikki.krogerus@linux.intel.com, lee.jones@linaro.org,
groeck@chromium.org, enric.balletbo@collabora.com,
tzungbi@kernel.org, sebastian.reichel@collabora.com,
gregkh@linuxfoundation.org, gustavoars@kernel.org,
bleung@chromium.org, dustin@howett.net, dnojiri@chromium.org,
tinghan.shen@mediatek.com, pmalani@chromium.org
Subject: Re: [PATCH v3] platform/chrome: cros_ec_typec: allow deferred probe of switch handles
Date: Thu, 26 Jan 2023 19:50:16 +0000 [thread overview]
Message-ID: <167476261680.7258.4736559242747511129.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230124075555.v3.1.I6c0a089123fdf143f94ef4cca8677639031856cf@changeid>
Hello:
This patch was applied to chrome-platform/linux.git (for-next)
by Prashant Malani <pmalani@chromium.org>:
On Tue, 24 Jan 2023 07:56:32 +0000 you wrote:
> `fwnode_typec_{retimer,mux,switch}_get()` could return `-EPROBE_DEFER`,
> which is called from `cros_typec_get_switch_handles`. When this happens,
> it does not indicate absence of switches; instead, it only hints that
> probing of switches should occur at a later time.
>
> Progagate `-EPROBE_DEFER` to upper layer logic so that they can re-try
> probing switches as a better time.
>
> [...]
Here is the summary with links:
- [v3] platform/chrome: cros_ec_typec: allow deferred probe of switch handles
https://git.kernel.org/chrome-platform/c/13aba1e532f0
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-01-26 19:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 7:56 [PATCH v3] platform/chrome: cros_ec_typec: allow deferred probe of switch handles Victor Ding
2023-01-24 13:20 ` Guenter Roeck
2023-01-24 14:09 ` Heikki Krogerus
2023-01-24 15:14 ` Benson Leung
2023-01-24 19:10 ` patchwork-bot+chrome-platform
2023-01-26 19:50 ` 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=167476261680.7258.4736559242747511129.git-patchwork-notify@kernel.org \
--to=patchwork-bot+chrome-platform@kernel.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=dnojiri@chromium.org \
--cc=dustin@howett.net \
--cc=enric.balletbo@collabora.com \
--cc=gregkh@linuxfoundation.org \
--cc=groeck@chromium.org \
--cc=gustavoars@kernel.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmalani@chromium.org \
--cc=sebastian.reichel@collabora.com \
--cc=tinghan.shen@mediatek.com \
--cc=tzungbi@kernel.org \
--cc=victording@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