All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Reichel <sebastian.reichel@collabora.com>
To: kbuild test robot <lkp@intel.com>
Cc: Tony Lindgren <tony@atomide.com>,
	kbuild-all@lists.01.org, linux-pm@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH power-supply] power: supply: cpcap-charger: cpcap_charger_voltage_to_regval() can be static
Date: Mon, 21 Oct 2019 11:05:04 +0200	[thread overview]
Message-ID: <20191021090504.qqkynac4jmxeru33@earth.universe> (raw)
In-Reply-To: <20191020222052.hud2r3jx2rvrrip3@4978f4969bb8>

[-- Attachment #1: Type: text/plain, Size: 1016 bytes --]

Hi,

On Mon, Oct 21, 2019 at 06:20:52AM +0800, kbuild test robot wrote:
> Fixes: d4ee021c410f ("power: supply: cpcap-charger: Limit voltage to 4.2V for battery")
> Signed-off-by: kbuild test robot <lkp@intel.com>
> ---

Thanks, I added a long description and queued it to power-supply's
-next branch. I did not fold it into the original patch, which is in
an immutable branch.

-- Sebastian

>  cpcap-charger.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/power/supply/cpcap-charger.c b/drivers/power/supply/cpcap-charger.c
> index 88bbab6e62f07..b4b7f9dc6c4ea 100644
> --- a/drivers/power/supply/cpcap-charger.c
> +++ b/drivers/power/supply/cpcap-charger.c
> @@ -478,7 +478,7 @@ static void cpcap_charger_update_state(struct cpcap_charger_ddata *ddata,
>  	dev_dbg(ddata->dev, "state: %s\n", status);
>  }
>  
> -int cpcap_charger_voltage_to_regval(int voltage)
> +static int cpcap_charger_voltage_to_regval(int voltage)
>  {
>  	int offset;
>  

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Sebastian Reichel <sebastian.reichel@collabora.com>
To: kbuild-all@lists.01.org
Subject: Re: [RFC PATCH power-supply] power: supply: cpcap-charger: cpcap_charger_voltage_to_regval() can be static
Date: Mon, 21 Oct 2019 11:05:04 +0200	[thread overview]
Message-ID: <20191021090504.qqkynac4jmxeru33@earth.universe> (raw)
In-Reply-To: <20191020222052.hud2r3jx2rvrrip3@4978f4969bb8>

[-- Attachment #1: Type: text/plain, Size: 1016 bytes --]

Hi,

On Mon, Oct 21, 2019 at 06:20:52AM +0800, kbuild test robot wrote:
> Fixes: d4ee021c410f ("power: supply: cpcap-charger: Limit voltage to 4.2V for battery")
> Signed-off-by: kbuild test robot <lkp@intel.com>
> ---

Thanks, I added a long description and queued it to power-supply's
-next branch. I did not fold it into the original patch, which is in
an immutable branch.

-- Sebastian

>  cpcap-charger.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/power/supply/cpcap-charger.c b/drivers/power/supply/cpcap-charger.c
> index 88bbab6e62f07..b4b7f9dc6c4ea 100644
> --- a/drivers/power/supply/cpcap-charger.c
> +++ b/drivers/power/supply/cpcap-charger.c
> @@ -478,7 +478,7 @@ static void cpcap_charger_update_state(struct cpcap_charger_ddata *ddata,
>  	dev_dbg(ddata->dev, "state: %s\n", status);
>  }
>  
> -int cpcap_charger_voltage_to_regval(int voltage)
> +static int cpcap_charger_voltage_to_regval(int voltage)
>  {
>  	int offset;
>  

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2019-10-21  9:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-20 22:20 [power-supply:for-next 18/29] drivers/power/supply/cpcap-charger.c:481:5: sparse: sparse: symbol 'cpcap_charger_voltage_to_regval' was not declared. Should it be static? kbuild test robot
2019-10-20 22:20 ` kbuild test robot
2019-10-20 22:20 ` [RFC PATCH power-supply] power: supply: cpcap-charger: cpcap_charger_voltage_to_regval() can be static kbuild test robot
2019-10-20 22:20   ` kbuild test robot
2019-10-21  9:05   ` Sebastian Reichel [this message]
2019-10-21  9:05     ` Sebastian Reichel

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=20191021090504.qqkynac4jmxeru33@earth.universe \
    --to=sebastian.reichel@collabora.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=tony@atomide.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 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.