public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Sangbeom Kim <sbkim73@samsung.com>,
	Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
	linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org
Subject: Re: [PATCH 1/2] mfd: sec-core: Cleanup formatting to a consistent style
Date: Fri, 1 Feb 2019 09:21:14 +0000	[thread overview]
Message-ID: <20190201092114.GE783@dell> (raw)
In-Reply-To: <1548761153-28114-1-git-send-email-krzk@kernel.org>

On Tue, 29 Jan 2019, Krzysztof Kozlowski wrote:

> Cleanup the formatting to have consistent style across the file (only
> white-space issues).  No expected difference in code.
> 
> Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
> ---
>  drivers/mfd/sec-core.c | 17 ++++++++++-------
>  1 file changed, 10 insertions(+), 7 deletions(-)
> 
> diff --git a/drivers/mfd/sec-core.c b/drivers/mfd/sec-core.c
> index e0835c9df7a1..c3bb53f79e63 100644
> --- a/drivers/mfd/sec-core.c
> +++ b/drivers/mfd/sec-core.c
> @@ -70,9 +70,11 @@ static const struct mfd_cell s2mps11_devs[] = {
>  };
>  
>  static const struct mfd_cell s2mps13_devs[] = {
> -	{ .name = "s2mps13-regulator", },
> -	{ .name = "s2mps13-rtc", },

I prefer one liners to remain on one line.

>  	{
> +		.name = "s2mps13-regulator",
> +	}, {
> +		.name = "s2mps13-rtc",
> +	}, {
>  		.name = "s2mps13-clk",
>  		.of_compatible = "samsung,s2mps13-clk",
>  	},
> @@ -114,7 +116,8 @@ static const struct mfd_cell s2mpu02_devs[] = {
>  
>  #ifdef CONFIG_OF
>  static const struct of_device_id sec_dt_match[] = {
> -	{	.compatible = "samsung,s5m8767-pmic",
> +	{
> +		.compatible = "samsung,s5m8767-pmic",
>  		.data = (void *)S5M8767X,

All of the other changes are fine.

>  	}, {
>  		.compatible = "samsung,s2mps11-pmic",
> @@ -309,8 +312,8 @@ static void sec_pmic_configure(struct sec_pmic_dev *sec_pmic)
>   * the sub-modules need not instantiate another instance while parsing their
>   * platform data.
>   */
> -static struct sec_platform_data *sec_pmic_i2c_parse_dt_pdata(
> -					struct device *dev)
> +static struct sec_platform_data *
> +sec_pmic_i2c_parse_dt_pdata(struct device *dev)
>  {
>  	struct sec_platform_data *pd;
>  
> @@ -331,8 +334,8 @@ static struct sec_platform_data *sec_pmic_i2c_parse_dt_pdata(
>  	return pd;
>  }
>  #else
> -static struct sec_platform_data *sec_pmic_i2c_parse_dt_pdata(
> -					struct device *dev)
> +static struct sec_platform_data *
> +sec_pmic_i2c_parse_dt_pdata(struct device *dev)
>  {
>  	return NULL;
>  }

-- 
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

  parent reply	other threads:[~2019-02-01  9:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-29 11:25 [PATCH 1/2] mfd: sec-core: Cleanup formatting to a consistent style Krzysztof Kozlowski
2019-01-29 11:25 ` [PATCH 2/2] mfd: sec-core: Return gracefully instead of BUG() if device cannot match Krzysztof Kozlowski
2019-02-01  9:22   ` Lee Jones
2019-02-01  9:21 ` Lee Jones [this message]
2019-02-11 13:14   ` [PATCH 1/2] mfd: sec-core: Cleanup formatting to a consistent style Krzysztof Kozlowski

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=20190201092114.GE783@dell \
    --to=lee.jones@linaro.org \
    --cc=b.zolnierkie@samsung.com \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=sbkim73@samsung.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