All of lore.kernel.org
 help / color / mirror / Atom feed
From: Liam Breck <liam@networkimprov.net>
To: Colin King <colin.king@canonical.com>
Cc: "Andrew F . Davis" <afd@ti.com>,
	Sebastian Reichel <sre@kernel.org>,
	linux-pm@vger.kernel.org
Subject: Re: [PATCH] power: supply: bq27xxx: make bq27xxx_battery_settings static
Date: Wed, 3 May 2017 23:30:51 -0700	[thread overview]
Message-ID: <CAKvHMgRGv_7VVgE+jio6L0uU86KRaL6sV2sSsTuRgwe9pF-OmQ@mail.gmail.com> (raw)
In-Reply-To: <20170503104554.23019-1-colin.king@canonical.com>

[dropped some CCs]

Hi Colin,

On Wed, May 3, 2017 at 3:45 AM, Colin King <colin.king@canonical.com> wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> The function bq27xxx_battery_settings can be made static as it
> does not need to be in global scope.

Thanks for flagging that. I've fixed it in the v13 series (just posted
to linux-pm); v12 landed in -next prematurely.


> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
>  drivers/power/supply/bq27xxx_battery.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/power/supply/bq27xxx_battery.c b/drivers/power/supply/bq27xxx_battery.c
> index 7152370b9d61..06f15da32464 100644
> --- a/drivers/power/supply/bq27xxx_battery.c
> +++ b/drivers/power/supply/bq27xxx_battery.c
> @@ -1251,7 +1251,7 @@ static void bq27xxx_battery_set_config(struct bq27xxx_device_info *di,
>         /* assume bq27xxx_battery_update() is called hereafter */
>  }
>
> -void bq27xxx_battery_settings(struct bq27xxx_device_info *di)
> +static void bq27xxx_battery_settings(struct bq27xxx_device_info *di)
>  {
>         struct power_supply_battery_info info = {};
>         unsigned int min, max;
> --
> 2.11.0
>

  reply	other threads:[~2017-05-04  6:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-03 10:45 [PATCH] power: supply: bq27xxx: make bq27xxx_battery_settings static Colin King
2017-05-03 10:45 ` Colin King
2017-05-04  6:30 ` Liam Breck [this message]
2017-05-04  8:10 ` Pali Rohár
2017-05-04  8:10   ` Pali Rohár
2017-05-04 15:24 ` Sebastian Reichel
2017-05-04 15:24   ` 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=CAKvHMgRGv_7VVgE+jio6L0uU86KRaL6sV2sSsTuRgwe9pF-OmQ@mail.gmail.com \
    --to=liam@networkimprov.net \
    --cc=afd@ti.com \
    --cc=colin.king@canonical.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=sre@kernel.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 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.