From: patchwork-bot+chrome-platform@kernel.org
To: =?utf-8?q?N=C3=ADcolas_F=2E_R=2E_A=2E_Prado_=3Cnfraprado=40collabora=2Ecom?=@ci.codeaurora.org,
=?utf-8?q?=3E?=@ci.codeaurora.org
Cc: pmalani@chromium.org, angelogioacchino.delregno@collabora.com,
kernel@collabora.com, bleung@chromium.org, groeck@chromium.org,
chrome-platform@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] platform/chrome: cros_ec_typec: Use dev_err_probe on port register fail
Date: Wed, 13 Jul 2022 17:30:13 +0000 [thread overview]
Message-ID: <165773341384.28136.7833622622098644174.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220712214554.545035-1-nfraprado@collabora.com>
Hello:
This patch was applied to chrome-platform/linux.git (for-kernelci)
by Prashant Malani <pmalani@chromium.org>:
On Tue, 12 Jul 2022 17:45:54 -0400 you wrote:
> The typec_register_port() can fail with EPROBE_DEFER if the endpoint
> node hasn't probed yet. In order to avoid spamming the log with errors
> in that case, log using dev_err_probe().
>
> Signed-off-by: Nícolas F. R. A. Prado <nfraprado@collabora.com>
>
>
> [...]
Here is the summary with links:
- platform/chrome: cros_ec_typec: Use dev_err_probe on port register fail
https://git.kernel.org/chrome-platform/c/ce838f7dc795
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-13 17:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 21:45 [PATCH] platform/chrome: cros_ec_typec: Use dev_err_probe on port register fail Nícolas F. R. A. Prado
2022-07-12 22:07 ` Guenter Roeck
2022-07-13 8:16 ` AngeloGioacchino Del Regno
2022-07-13 17:30 ` patchwork-bot+chrome-platform [this message]
2022-07-15 19:00 ` 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=165773341384.28136.7833622622098644174.git-patchwork-notify@kernel.org \
--to=patchwork-bot+chrome-platform@kernel.org \
--cc==?utf-8?q?=3E?=@ci.codeaurora.org \
--cc==?utf-8?q?N=C3=ADcolas_F=2E_R=2E_A=2E_Prado_=3Cnfraprado=40collabora=2Ecom?=@ci.codeaurora.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=groeck@chromium.org \
--cc=kernel@collabora.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