From: patchwork-bot+chrome-platform@kernel.org
To: Tzung-Bi Shih <tzungbi@kernel.org>
Cc: bleung@chromium.org, groeck@chromium.org,
chrome-platform@lists.linux.dev, robertzieba@google.com,
markhas@chromium.org, bhanumaiya@chromium.org
Subject: Re: [PATCH] platform/chrome: cros_ec_uart: fix race condition
Date: Tue, 03 Jan 2023 05:40:16 +0000 [thread overview]
Message-ID: <167272441649.10584.9545890058713452896.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221229094738.2304044-1-tzungbi@kernel.org>
Hello:
This patch was applied to chrome-platform/linux.git (for-kernelci)
by Tzung-Bi Shih <tzungbi@kernel.org>:
On Thu, 29 Dec 2022 17:47:38 +0800 you wrote:
> From: Robert Zieba <robertzieba@google.com>
>
> serdev_device_set_client_ops() is called before `ec_dev` is fully
> initialized. This can result in cros_ec_uart_rx_bytes() being called
> while `ec_dev` is still not initialized, resulting in a kernel panic.
>
> Call serdev_device_set_client_ops() after `ec_dev` is initialized.
>
> [...]
Here is the summary with links:
- platform/chrome: cros_ec_uart: fix race condition
https://git.kernel.org/chrome-platform/c/56d4b33d45e3
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:[~2023-01-03 5:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-29 9:47 [PATCH] platform/chrome: cros_ec_uart: fix race condition Tzung-Bi Shih
2022-12-29 16:57 ` Mark Hasemeyer
2022-12-29 20:09 ` Guenter Roeck
2023-01-03 18:33 ` Mark Hasemeyer
2022-12-29 20:07 ` Guenter Roeck
2023-01-03 5:40 ` patchwork-bot+chrome-platform [this message]
2023-01-03 8:10 ` 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=167272441649.10584.9545890058713452896.git-patchwork-notify@kernel.org \
--to=patchwork-bot+chrome-platform@kernel.org \
--cc=bhanumaiya@chromium.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=groeck@chromium.org \
--cc=markhas@chromium.org \
--cc=robertzieba@google.com \
--cc=tzungbi@kernel.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