From: "Andrew F. Davis" <afd@ti.com>
To: Sebastian Reichel <sre@kernel.org>
Cc: "H. Nikolaus Schaller" <hns@goldelico.com>,
"Pali Rohár" <pali.rohar@gmail.com>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
gta04-owner@goldelico.com, marek@goldelico.com
Subject: Re: [PATCH 0/2] two fixes for new bq27000/10 and bq27500 driver
Date: Thu, 24 Dec 2015 07:57:56 -0600 [thread overview]
Message-ID: <567BF9E4.20105@ti.com> (raw)
In-Reply-To: <20151219080048.GA11317@earth>
On 12/19/2015 02:00 AM, Sebastian Reichel wrote:
> Hi Andrew,
>
> On Thu, Dec 17, 2015 at 11:12:52AM +0100, H. Nikolaus Schaller wrote:
>> H. Nikolaus Schaller (2):
>> power:bq27xxx: fix reading for bq27000 and bq27010
>> power:bq27xxx: fix register numbers of bq27500
>>
>> drivers/power/bq27xxx_battery.c | 18 ++++++++++++------
>> 1 file changed, 12 insertions(+), 6 deletions(-)
>
> Can you give me your Acked-By (or Tested-By) for those patches?
Done
> Also I wonder if you would be available as official reviewer for
> the driver.
Sure, what's the normal procedure for this, should I submit a
patch adding myself to that driver in MAINTAINERS?
next prev parent reply other threads:[~2015-12-24 13:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 10:12 [PATCH 0/2] two fixes for new bq27000/10 and bq27500 driver H. Nikolaus Schaller
2015-12-17 10:12 ` [PATCH 1/2] power:bq27xxx: fix reading for bq27000 and bq27010 H. Nikolaus Schaller
2015-12-24 2:46 ` Andrew F. Davis
2015-12-25 13:20 ` Pali Rohár
2015-12-17 10:12 ` [PATCH 2/2] power:bq27xxx: fix register numbers of bq27500 H. Nikolaus Schaller
2015-12-24 2:52 ` Andrew F. Davis
2015-12-19 8:00 ` [PATCH 0/2] two fixes for new bq27000/10 and bq27500 driver Sebastian Reichel
2015-12-24 13:57 ` Andrew F. Davis [this message]
2015-12-25 13:22 ` Pali Rohár
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=567BF9E4.20105@ti.com \
--to=afd@ti.com \
--cc=gta04-owner@goldelico.com \
--cc=hns@goldelico.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=marek@goldelico.com \
--cc=pali.rohar@gmail.com \
--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 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).