mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Steve Twiss <stwiss.opensource@diasemi.com>
Cc: LINUX-KERNEL <linux-kernel@vger.kernel.org>,
	Support Opensource <support.opensource@diasemi.com>
Subject: Re: [PATCH V1] mfd: da9062: use core helper regmap_reg_range macros
Date: Wed, 28 Mar 2018 16:29:55 +0100	[thread overview]
Message-ID: <20180328152955.qrbga5fgo3ls6eje@dell> (raw)
In-Reply-To: <20180328110612.1FCAD3FACC@swsrvapps-01.diasemi.com>

On Wed, 28 Mar 2018, Steve Twiss wrote:

> From: Steve Twiss <stwiss.opensource@diasemi.com>
> 
> Replace multi-line entries in the regmap_range arrays with single
> line macros: regmap_reg_range(). This will leave the static structure
> array entries for regmap_range unaltered. It will significantly reduce
> the line count in the DA9062/61 core file.
> 
> Signed-off-by: Steve Twiss <stwiss.opensource@diasemi.com>
> 
> ---
> This patch applies against linux-next and v4.16-rc7
> 
> Hi,
> 
> This is a cosmetic tidy up operation. It reduces the line-count in the
> file by over 200.
> 
> It will replace regmap_range[] array entries, such as this: 
> {
>   .range_min = DA9062AA_DEVICE_ID,
>   .range_max = DA9062AA_CONFIG_ID,
> },
> 
> with a single line,
>  regmap_reg_range(DA9062AA_DEVICE_ID, DA9062AA_CONFIG_ID),
> 
> Regards,
> Steve Twiss, Dialog Semiconductor
> 
> 
>  drivers/mfd/da9062-core.c | 462 ++++++++++++----------------------------------
>  1 file changed, 114 insertions(+), 348 deletions(-)

Nice!

Applied, thanks.

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

      reply	other threads:[~2018-03-28 15:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-28 11:03 Steve Twiss
2018-03-28 15:29 ` Lee Jones [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=20180328152955.qrbga5fgo3ls6eje@dell \
    --to=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stwiss.opensource@diasemi.com \
    --cc=support.opensource@diasemi.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®