Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/4] Set name of regmap_config
Date: Fri, 9 Mar 2018 08:16:03 +0000	[thread overview]
Message-ID: <20180309081603.4u5pgwwsfxernodm@dell> (raw)
In-Reply-To: <20180309015146.8297-1-jeffy.chen@rock-chips.com>

On Fri, 09 Mar 2018, Jeffy Chen wrote:

> 
> After 9b947a13e7f6 ("regmap: use debugfs even when no device"), we are
> allowing regmap to create debugfs without a valid device. Some of them
> would end up using "dummy*" as debugfs name.
> 
> This series try to set names in some regmap_config to avoid that.
> 
> 
> Changes in v4:
> Not to use rtc dev to init regmap, the gpbr is not directly related to
> the rtc.
> 
> Changes in v3:
> Modify commit message.
> 
> Jeffy Chen (4):
>   mfd: syscon: Set name of regmap_config
>   rtc: at91sam9: Set name of regmap_config
>   clk: lpc32xx: Set name of regmap_config
>   ARM: rockchip: Set name of regmap_config
> 
>  arch/arm/mach-rockchip/platsmp.c | 1 +
>  drivers/clk/nxp/clk-lpc32xx.c    | 1 +
>  drivers/mfd/syscon.c             | 1 +

It's difficult to review, since we cannot see what's happening with
the rest of the patch set.  Would you mind re-sending the whole set to
all parties please?

>  drivers/rtc/rtc-at91sam9.c       | 1 +
>  4 files changed, 4 insertions(+)
> 

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

  parent reply	other threads:[~2018-03-09  8:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-09  1:51 [PATCH v4 0/4] Set name of regmap_config Jeffy Chen
2018-03-09  1:51 ` [PATCH v4 2/4] rtc: at91sam9: " Jeffy Chen
2018-03-09  1:51 ` [PATCH v4 3/4] clk: lpc32xx: " Jeffy Chen
2018-03-09  1:51 ` [PATCH v4 4/4] ARM: rockchip: " Jeffy Chen
2018-03-09  8:16 ` Lee Jones [this message]
2018-03-09  8:45   ` [PATCH v4 0/4] " JeffyChen

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=20180309081603.4u5pgwwsfxernodm@dell \
    --to=lee.jones@linaro.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox