From: Subhash Jadavani <subhashj@codeaurora.org>
To: kusumi.tomohiro@gmail.com
Cc: vinholikatti@gmail.com, linux-scsi@vger.kernel.org,
Tomohiro Kusumi <tkusumi@tuxera.com>,
linux-scsi-owner@vger.kernel.org
Subject: Re: [PATCH] scsi: ufs: fix wrong/ambiguous fall through comments
Date: Fri, 24 Mar 2017 16:21:13 -0700 [thread overview]
Message-ID: <59298e05e511ed5860e07e48fc55f173@codeaurora.org> (raw)
In-Reply-To: <20170323104904.47040-1-tkusumi@tuxera.com>
On 2017-03-23 03:49, kusumi.tomohiro@gmail.com wrote:
> From: Tomohiro Kusumi <tkusumi@tuxera.com>
>
> These aren't really falling through to anywhere meaningful.
>
> Signed-off-by: Tomohiro Kusumi <tkusumi@tuxera.com>
> ---
> drivers/scsi/ufs/ufshcd.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/scsi/ufs/ufshcd.c b/drivers/scsi/ufs/ufshcd.c
> index dc6efbd..b7e5128 100644
> --- a/drivers/scsi/ufs/ufshcd.c
> +++ b/drivers/scsi/ufs/ufshcd.c
> @@ -553,15 +553,14 @@ static inline u32 ufshcd_get_intr_mask(struct
> ufs_hba *hba)
> case UFSHCI_VERSION_10:
> intr_mask = INTERRUPT_MASK_ALL_VER_10;
> break;
> - /* allow fall through */
> case UFSHCI_VERSION_11:
> case UFSHCI_VERSION_20:
> intr_mask = INTERRUPT_MASK_ALL_VER_11;
> break;
> - /* allow fall through */
> case UFSHCI_VERSION_21:
> default:
> intr_mask = INTERRUPT_MASK_ALL_VER_21;
> + break;
> }
>
> return intr_mask;
Looks good to me.
Reviewed-by: Subhash Jadavani <subhashj@codeaurora.org>
--
The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2017-03-24 23:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-23 10:49 [PATCH] scsi: ufs: fix wrong/ambiguous fall through comments kusumi.tomohiro
2017-03-24 23:21 ` Subhash Jadavani [this message]
2017-03-28 1:56 ` Martin K. Petersen
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=59298e05e511ed5860e07e48fc55f173@codeaurora.org \
--to=subhashj@codeaurora.org \
--cc=kusumi.tomohiro@gmail.com \
--cc=linux-scsi-owner@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=tkusumi@tuxera.com \
--cc=vinholikatti@gmail.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;
as well as URLs for NNTP newsgroup(s).