devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Stefan Popa <stefan.popa@analog.com>,
	sre@kernel.org, robh+dt@kernel.org, mark.rutland@arm.com
Cc: davem@davemloft.net, mchehab@kernel.org,
	gregkh@linuxfoundation.org, linus.walleij@linaro.org,
	akpm@linux-foundation.org, linux-pm@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] adp5061: New driver for ADP5061 I2C battery charger
Date: Wed, 4 Apr 2018 10:33:56 -0700	[thread overview]
Message-ID: <66d5534b-d383-733e-8e56-992dfec6ee90@infradead.org> (raw)
In-Reply-To: <1522829832-7866-1-git-send-email-stefan.popa@analog.com>

Hi,
one small typo below:

On 04/04/2018 01:17 AM, Stefan Popa wrote:

> diff --git a/drivers/power/supply/Kconfig b/drivers/power/supply/Kconfig
> index 428b426..761cc52 100644
> --- a/drivers/power/supply/Kconfig
> +++ b/drivers/power/supply/Kconfig
> @@ -75,6 +75,17 @@ config BATTERY_88PM860X
>  	help
>  	  Say Y here to enable battery monitor for Marvell 88PM860x chip.
>  
> +config CHARGER_ADP5061
> +	tristate "ADP5061 battery charger driver"
> +	depends on I2C
> +	select REGMAP_I2C
> +	help
> +	  Say Y here to enable support for the ADP5061 standalone battery
> +	  charger.
> +
> +	  This driver can be build as a module. If so, the module will be

	                     built

> +	  called adp5061.
> +
>  config BATTERY_ACT8945A
>  	tristate "Active-semi ACT8945A charger driver"
>  	depends on MFD_ACT8945A || COMPILE_TEST


-- 
~Randy

  reply	other threads:[~2018-04-04 17:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-04  8:17 [PATCH 1/3] adp5061: New driver for ADP5061 I2C battery charger Stefan Popa
2018-04-04 17:33 ` Randy Dunlap [this message]
2018-04-10  9:49 ` [PATCH v2 " Stefan Popa
2018-04-10 13:50 ` [PATCH " Rob Herring
2018-04-11 15:10 ` [PATCH v3 2/4] dt-bindings:power:supply: Add docs for ADP5061 " Stefan Popa
2018-04-13 21:06   ` Rob Herring

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=66d5534b-d383-733e-8e56-992dfec6ee90@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mchehab@kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=sre@kernel.org \
    --cc=stefan.popa@analog.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;
as well as URLs for NNTP newsgroup(s).