From: Bart Van Assche <bvanassche@acm.org>
To: Hongjie Fang <hongjiefang@asrmicro.com>,
alim.akhtar@samsung.com, avri.altman@wdc.com,
James.Bottomley@HansenPartnership.com,
martin.petersen@oracle.com
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] scsi: ufs: core: call hibern8 notify when hibern8 cmd failed
Date: Thu, 30 Apr 2026 10:30:55 -0700 [thread overview]
Message-ID: <26d908a7-8f95-4f73-b2bf-78923e55b3e8@acm.org> (raw)
In-Reply-To: <20260430042212.3712251-1-hongjiefang@asrmicro.com>
On 4/29/26 9:22 PM, Hongjie Fang wrote:
> diff --git a/include/ufs/ufshcd.h b/include/ufs/ufshcd.h
> index 8563b6648976..4f7c619db324 100644
> --- a/include/ufs/ufshcd.h
> +++ b/include/ufs/ufshcd.h
> @@ -270,6 +270,7 @@ struct ufs_clk_info {
> enum ufs_notify_change_status {
> PRE_CHANGE,
> POST_CHANGE,
> + ROLLBACK_CHANGE,
> };
>
> struct ufs_pa_layer_attr {
This looks better to me but triggers compiler warnings:
drivers/ufs/host/ufs-exynos.c:1614:10: error: enumeration value
'ROLLBACK_CHANGE' not handled in switch [-Werror,-Wswitch]
1614 | switch (status) {
| ^~~~~~
drivers/ufs/host/ufs-exynos.c:1654:10: error: enumeration value
'ROLLBACK_CHANGE' not handled in switch [-Werror,-Wswitch]
1654 | switch (status) {
| ^~~~~~
drivers/ufs/host/ufs-exynos.c:1687:10: error: enumeration value
'ROLLBACK_CHANGE' not handled in switch [-Werror,-Wswitch]
1687 | switch (status) {
| ^~~~~~
These warnings can be reproduced on any Linux development system by
installing Clang and by running the following command:
build-scsi-drivers -c
See also https://github.com/bvanassche/build-scsi-drivers
Thanks,
Bart.
next prev parent reply other threads:[~2026-04-30 17:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 4:22 [PATCH v3] scsi: ufs: core: call hibern8 notify when hibern8 cmd failed Hongjie Fang
2026-04-30 17:30 ` Bart Van Assche [this message]
2026-05-01 12:53 ` Fang Hongjie(方洪杰)
2026-05-02 10:05 ` kernel test robot
2026-05-02 13:57 ` kernel test robot
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=26d908a7-8f95-4f73-b2bf-78923e55b3e8@acm.org \
--to=bvanassche@acm.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=hongjiefang@asrmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox