From: Grazvydas Ignotas <notasas@gmail.com>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: Anton Vorontsov <cbouatmailru@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: bq27x00_battery status report issue
Date: Fri, 20 Jan 2012 13:02:46 +0200 [thread overview]
Message-ID: <CANOLnOOAwyM=Egzr_S8pUa=6iM=q8TU8jRJW_5nVrgqtqLHGxw@mail.gmail.com> (raw)
In-Reply-To: <10055259.ygSgKeUM8f@pali>
On Thu, Jan 19, 2012 at 12:56 PM, Pali Rohár <pali.rohar@gmail.com> wrote:
> Now I do not have device with bq27500 chip for testing. I read datasheet again
> and I think that your interpretation may be correct. Can you write patch for
> this problem and test it?
What about just reverting 270968c0984ae instead? I think my patch
would look almost exactly like that..
--
Gražvydas
next prev parent reply other threads:[~2012-01-20 11:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-14 21:10 bq27x00_battery status report issue Grazvydas Ignotas
2012-01-19 10:56 ` Pali Rohár
2012-01-20 11:02 ` Grazvydas Ignotas [this message]
2012-01-20 13:38 ` Pali Rohár
2012-02-01 17:37 ` Anton Vorontsov
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='CANOLnOOAwyM=Egzr_S8pUa=6iM=q8TU8jRJW_5nVrgqtqLHGxw@mail.gmail.com' \
--to=notasas@gmail.com \
--cc=cbouatmailru@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pali.rohar@gmail.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).