From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [patch] spi: pxa2xx: missing break in pxa2xx_ssp_get_clk_div()
Date: Mon, 30 Mar 2015 10:55:12 +0000 [thread overview]
Message-ID: <1427712912.14897.441.camel@linux.intel.com> (raw)
In-Reply-To: <20150330103040.GB27144@mwanda>
On Mon, 2015-03-30 at 13:30 +0300, Dan Carpenter wrote:
> We refactored this code but accidentally left out a break statement so
> QUARK_X1000_SSP isn't handled correctly.
>
Thanks for catching this!
One comment below.
> Fixes: 025ffe88ee60 ('spi: pxa2xx: shift clk_div in one place')
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
>
> diff --git a/drivers/spi/spi-pxa2xx.c b/drivers/spi/spi-pxa2xx.c
> index 60526a5..a081cfc 100644
> --- a/drivers/spi/spi-pxa2xx.c
> +++ b/drivers/spi/spi-pxa2xx.c
> @@ -791,6 +791,7 @@ static unsigned int pxa2xx_ssp_get_clk_div(struct driver_data *drv_data,
> switch (drv_data->ssp_type) {
> case QUARK_X1000_SSP:
> clk_div = quark_x1000_get_clk_div(rate, &chip->dds_rate);
> + break;
> default:
> clk_div = ssp_get_clk_div(drv_data, rate);
It would be nice to have a break here as well, but I think we also may
change this to if-else-if construction.
> }
Whatever solution you choose
Acked-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
And actually
Tested-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Now run with time to see the difference.
--
Andy Shevchenko <andriy.shevchenko@intel.com>
Intel Finland Oy
WARNING: multiple messages have this Message-ID (diff)
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Mark Brown <broonie@kernel.org>,
Haojian Zhuang <haojian.zhuang@gmail.com>,
Robert Jarzmik <robert.jarzmik@free.fr>,
Daniel Mack <daniel@zonque.org>,
linux-arm-kernel@lists.infradead.org, linux-spi@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [patch] spi: pxa2xx: missing break in pxa2xx_ssp_get_clk_div()
Date: Mon, 30 Mar 2015 13:55:12 +0300 [thread overview]
Message-ID: <1427712912.14897.441.camel@linux.intel.com> (raw)
In-Reply-To: <20150330103040.GB27144@mwanda>
On Mon, 2015-03-30 at 13:30 +0300, Dan Carpenter wrote:
> We refactored this code but accidentally left out a break statement so
> QUARK_X1000_SSP isn't handled correctly.
>
Thanks for catching this!
One comment below.
> Fixes: 025ffe88ee60 ('spi: pxa2xx: shift clk_div in one place')
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
>
> diff --git a/drivers/spi/spi-pxa2xx.c b/drivers/spi/spi-pxa2xx.c
> index 60526a5..a081cfc 100644
> --- a/drivers/spi/spi-pxa2xx.c
> +++ b/drivers/spi/spi-pxa2xx.c
> @@ -791,6 +791,7 @@ static unsigned int pxa2xx_ssp_get_clk_div(struct driver_data *drv_data,
> switch (drv_data->ssp_type) {
> case QUARK_X1000_SSP:
> clk_div = quark_x1000_get_clk_div(rate, &chip->dds_rate);
> + break;
> default:
> clk_div = ssp_get_clk_div(drv_data, rate);
It would be nice to have a break here as well, but I think we also may
change this to if-else-if construction.
> }
Whatever solution you choose
Acked-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
And actually
Tested-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Now run with time to see the difference.
--
Andy Shevchenko <andriy.shevchenko@intel.com>
Intel Finland Oy
WARNING: multiple messages have this Message-ID (diff)
From: andriy.shevchenko@linux.intel.com (Andy Shevchenko)
To: linux-arm-kernel@lists.infradead.org
Subject: [patch] spi: pxa2xx: missing break in pxa2xx_ssp_get_clk_div()
Date: Mon, 30 Mar 2015 13:55:12 +0300 [thread overview]
Message-ID: <1427712912.14897.441.camel@linux.intel.com> (raw)
In-Reply-To: <20150330103040.GB27144@mwanda>
On Mon, 2015-03-30 at 13:30 +0300, Dan Carpenter wrote:
> We refactored this code but accidentally left out a break statement so
> QUARK_X1000_SSP isn't handled correctly.
>
Thanks for catching this!
One comment below.
> Fixes: 025ffe88ee60 ('spi: pxa2xx: shift clk_div in one place')
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
>
> diff --git a/drivers/spi/spi-pxa2xx.c b/drivers/spi/spi-pxa2xx.c
> index 60526a5..a081cfc 100644
> --- a/drivers/spi/spi-pxa2xx.c
> +++ b/drivers/spi/spi-pxa2xx.c
> @@ -791,6 +791,7 @@ static unsigned int pxa2xx_ssp_get_clk_div(struct driver_data *drv_data,
> switch (drv_data->ssp_type) {
> case QUARK_X1000_SSP:
> clk_div = quark_x1000_get_clk_div(rate, &chip->dds_rate);
> + break;
> default:
> clk_div = ssp_get_clk_div(drv_data, rate);
It would be nice to have a break here as well, but I think we also may
change this to if-else-if construction.
> }
Whatever solution you choose
Acked-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
And actually
Tested-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Now run with time to see the difference.
--
Andy Shevchenko <andriy.shevchenko@intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2015-03-30 10:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 10:30 [patch] spi: pxa2xx: missing break in pxa2xx_ssp_get_clk_div() Dan Carpenter
2015-03-30 10:30 ` Dan Carpenter
2015-03-30 10:30 ` Dan Carpenter
2015-03-30 10:55 ` Andy Shevchenko [this message]
2015-03-30 10:55 ` Andy Shevchenko
2015-03-30 10:55 ` Andy Shevchenko
2015-03-31 8:49 ` Mark Brown
2015-03-31 8:49 ` Mark Brown
2015-03-31 8:49 ` Mark Brown
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=1427712912.14897.441.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.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 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.