From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mfd: ab8500: add static linkage for battery info
Date: Fri, 23 Nov 2012 09:55:16 +0000 [thread overview]
Message-ID: <20121123095516.GJ17471@gmail.com> (raw)
In-Reply-To: <20121123094800.GH17471@gmail.com>
> How do you want this patch to be treated?
>
> Is this a patch or a branch? If it's a branch, why are you referencing
> it? Have you issued a pull request? If it's a patch (I'm assuming it
> hasn't been accepted yet), then you should just fix it up into the
> patch.
My apologies, I've just seen Anton's message to you.
> > From: "Rajanikanth H.V" <rajanikanth.hv@linaro.org>
> >
> > enforce static linkage for battery attributes structures
<subsystem>: Enforce static linkage for battery attributes structures
^
Capital letter to start a sentence.
It's always worth doing `git log --oneline <subsystem>` to see how
the maintainer likes their $SUBJECT lines to be structured.
> > this patch is against: "mfd-ab8500-add-devicetree-support-for-fuelgauge"
There's no need to say this, please remove this line.
You also need a short description of what you're actually doing
in the patch.
> > Signed-off-by: Rajanikanth H.V <rajanikanth.hv@linaro.org>
> > ---
> > drivers/power/ab8500_bmdata.c | 6 +++---
> > 1 file changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/drivers/power/ab8500_bmdata.c b/drivers/power/ab8500_bmdata.c
> > index ff8f055..db17930 100644
> > --- a/drivers/power/ab8500_bmdata.c
> > +++ b/drivers/power/ab8500_bmdata.c
> > @@ -143,7 +143,7 @@ static struct abx500_res_to_temp temp_tbl[] = {
> > * Note that the batres_vs_temp table must be strictly sorted by falling
> > * temperature values to work.
> > */
> > -struct batres_vs_temp temp_to_batres_tbl_thermistor[] = {
> > +static struct batres_vs_temp temp_to_batres_tbl_thermistor[] = {
> > { 40, 120},
> > { 30, 135},
> > { 20, 165},
> > @@ -157,7 +157,7 @@ struct batres_vs_temp temp_to_batres_tbl_thermistor[] = {
> > * Note that the batres_vs_temp table must be strictly sorted by falling
> > * temperature values to work.
> > */
> > -struct batres_vs_temp temp_to_batres_tbl_ext_thermistor[] = {
> > +static struct batres_vs_temp temp_to_batres_tbl_ext_thermistor[] = {
> > { 60, 300},
> > { 30, 300},
> > { 20, 300},
> > @@ -168,7 +168,7 @@ struct batres_vs_temp temp_to_batres_tbl_ext_thermistor[] = {
> > };
> >
> > /* battery resistance table for LI ION 9100 battery */
> > -struct batres_vs_temp temp_to_batres_tbl_9100[] = {
> > +static struct batres_vs_temp temp_to_batres_tbl_9100[] = {
> > { 60, 180},
> > { 30, 180},
> > { 20, 180},
> > --
> > 1.7.10.4
> >
>
> --
> Lee Jones
> Linaro ST-Ericsson Landing Team Lead
> Linaro.org ? Open source software for ARM SoCs
> Follow Linaro: Facebook | Twitter | Blog
--
Lee Jones
Linaro ST-Ericsson Landing Team Lead
Linaro.org ? Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
prev parent reply other threads:[~2012-11-23 9:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-23 4:14 [PATCH] mfd: ab8500: add static linkage for battery info Rajanikanth H.V
2012-11-23 9:48 ` Lee Jones
2012-11-23 9:55 ` 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=20121123095516.GJ17471@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).