From: patchwork-bot+chrome-platform@kernel.org
To: Yuan Can <yuancan@huawei.com>
Cc: pmalani@chromium.org, bleung@chromium.org, gwendal@chromium.org,
jflat@chromium.org, chrome-platform@lists.linux.dev
Subject: Re: [PATCH] platform/chrome: cros_usbpd_notify: Fix error handling in cros_usbpd_notify_init()
Date: Mon, 28 Nov 2022 20:00:16 +0000 [thread overview]
Message-ID: <166966561698.11611.4134873993450346997.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221117080823.77549-1-yuancan@huawei.com>
Hello:
This patch was applied to chrome-platform/linux.git (for-next)
by Prashant Malani <pmalani@chromium.org>:
On Thu, 17 Nov 2022 08:08:23 +0000 you wrote:
> The following WARNING message was given when rmmod cros_usbpd_notify:
>
> Unexpected driver unregister!
> WARNING: CPU: 0 PID: 253 at drivers/base/driver.c:270 driver_unregister+0x8a/0xb0
> Modules linked in: cros_usbpd_notify(-)
> CPU: 0 PID: 253 Comm: rmmod Not tainted 6.1.0-rc3 #24
> ...
> Call Trace:
> <TASK>
> cros_usbpd_notify_exit+0x11/0x1e [cros_usbpd_notify]
> __x64_sys_delete_module+0x3c7/0x570
> ? __ia32_sys_delete_module+0x570/0x570
> ? lock_is_held_type+0xe3/0x140
> ? syscall_enter_from_user_mode+0x17/0x50
> ? rcu_read_lock_sched_held+0xa0/0xd0
> ? syscall_enter_from_user_mode+0x1c/0x50
> do_syscall_64+0x37/0x90
> entry_SYSCALL_64_after_hwframe+0x63/0xcd
> RIP: 0033:0x7f333fe9b1b7
>
> [...]
Here is the summary with links:
- platform/chrome: cros_usbpd_notify: Fix error handling in cros_usbpd_notify_init()
https://git.kernel.org/chrome-platform/c/5a2d96623670
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:[~2022-11-28 20:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 8:08 [PATCH] platform/chrome: cros_usbpd_notify: Fix error handling in cros_usbpd_notify_init() Yuan Can
2022-11-17 19:07 ` Prashant Malani
2022-11-18 10:18 ` Yuan Can
2022-11-18 20:11 ` Prashant Malani
2022-11-23 8:33 ` Yuan Can
2022-11-25 8:27 ` Prashant Malani
2022-11-17 19:15 ` Brian Norris
2022-11-25 8:40 ` patchwork-bot+chrome-platform
2022-11-28 20:00 ` 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=166966561698.11611.4134873993450346997.git-patchwork-notify@kernel.org \
--to=patchwork-bot+chrome-platform@kernel.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=gwendal@chromium.org \
--cc=jflat@chromium.org \
--cc=pmalani@chromium.org \
--cc=yuancan@huawei.com \
/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.