From: Richard Fitzgerald <rf@opensource.cirrus.com>
To: Progyan Bhattacharya <bprogyan@gmail.com>,
<linux-kernel@vger.kernel.org>
Cc: Lee Jones <lee.jones@linaro.org>, <patches@opensource.cirrus.com>
Subject: Re: [PATCH] Drivers/mfd: Remove Non-standard Case Statements
Date: Thu, 15 Feb 2018 16:25:49 +0000 [thread overview]
Message-ID: <f90497b0-89b9-f07f-3951-9a2fcd9073ae@opensource.cirrus.com> (raw)
In-Reply-To: <20180215160441.4548-1-progyanb@acm.org>
On 15/02/18 16:04, Progyan Bhattacharya wrote:
> Remove Range Expressions from Case Statements and replace them with equivalent If-Else ladder. Comments are kept as is for understanding.
>
Why?
Your commit message should at least say why you are making this change.
(It also should be wrapped to a sensible line length).
The "case x ... y:" style is used in many places all over the kernel. As
are other gcc extensions.
Is this a change in kernel coding style guidelines? Or are you trying to
make it a compile with a different compiler to normal?
Although I'm not a fan of non-standard C extensions, in my opinion the
case ... is more readable than the chain of if statements.
> Signed-off-by: Progyan Bhattacharya <progyanb@acm.org>
> Cc: Lee Jones <lee.jones@linaro.org>
> Cc: patches@opensource.cirrus.com
> Cc: linux-kernel@vger.kernel.org
> ---
> drivers/mfd/cs47l24-tables.c | 30 +++++++++++++++++-------------
> 1 file changed, 17 insertions(+), 13 deletions(-)
>
> diff --git a/drivers/mfd/cs47l24-tables.c b/drivers/mfd/cs47l24-tables.c
> index c090974340ad..99eeb6bac5d5 100644
> --- a/drivers/mfd/cs47l24-tables.c
> +++ b/drivers/mfd/cs47l24-tables.c
> @@ -783,19 +783,23 @@ static const struct reg_default cs47l24_reg_default[] = {
>
> static bool cs47l24_is_adsp_memory(unsigned int reg)
> {
> - switch (reg) {
> - case 0x200000 ... 0x205fff: /* DSP2 PM */
> - case 0x280000 ... 0x281fff: /* DSP2 ZM */
> - case 0x290000 ... 0x2a7fff: /* DSP2 XM */
> - case 0x2a8000 ... 0x2b3fff: /* DSP2 YM */
> - case 0x300000 ... 0x308fff: /* DSP3 PM */
> - case 0x380000 ... 0x381fff: /* DSP3 ZM */
> - case 0x390000 ... 0x3a7fff: /* DSP3 XM */
> - case 0x3a8000 ... 0x3b3fff: /* DSP3 YM */
> - return true;
> - default:
> - return false;
> - }
> + if (reg >= 0x200000 && reg <= 0x205fff) /* DSP2 PM */
> + return true;
> + if (reg >= 0x280000 && reg <= 0x281fff) /* DSP2 ZM */
> + return true;
> + if (reg >= 0x290000 && reg <= 0x2a7fff) /* DSP2 XM */
> + return true;
> + if (reg >= 0x2a8000 && reg <= 0x2b3fff) /* DSP2 YM */
> + return true;
> + if (reg <= 0x300000 && reg >= 0x308fff) /* DSP3 PM */
> + return true;
> + if (reg <= 0x380000 && reg >= 0x381fff) /* DSP3 ZM */
> + return true;
> + if (reg <= 0x390000 && reg >= 0x3a7fff) /* DSP3 XM */
> + return true;
> + if (reg <= 0x3a8000 && reg >= 0x3b3fff) /* DSP3 YM */
> + return true;
> + return false;
> }
>
> static bool cs47l24_readable_register(struct device *dev, unsigned int reg)
>
prev parent reply other threads:[~2018-02-15 16:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 16:04 Progyan Bhattacharya
2018-02-15 16:25 ` Richard Fitzgerald [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=f90497b0-89b9-f07f-3951-9a2fcd9073ae@opensource.cirrus.com \
--to=rf@opensource.cirrus.com \
--cc=bprogyan@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.cirrus.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
all inboxes | Powered by JetHome®