From: Evgeniy Polyakov <zbr@ioremap.net>
To: Sebastian Reichel <sebastian.reichel@collabora.co.uk>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] power: supply: move HDQ interface for bq27xxx from w1 to power/supply
Date: Sun, 27 Aug 2017 10:25:34 +0300 [thread overview]
Message-ID: <1195431503818734@web4g.yandex.ru> (raw)
In-Reply-To: <20170725134827.wxlkoebcwh5ycnk3@earth>
Hi everyone
Sorry for long delay
25.07.2017, 16:48, "Sebastian Reichel" <sebastian.reichel@collabora.co.uk>:
> Here is a signed immutable branch for Andrew's patch, which moves
> bq27000 w1 driver to the power-supply subsystem. I guess git will
> figure everything out without this, but better safe than sorry :)
>
> The following changes since commit 520eccdfe187591a51ea9ab4c1a024ae4d0f68d9:
>
> Linux 4.13-rc2 (2017-07-23 16:15:17 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/sre/linux-power-supply.git tags/ib-w1-bq27000-4.14
>
> for you to fetch changes up to 55a9db679183bcf85a6e5c44a4f92f158bb6f03d:
>
> power: supply: move HDQ interface for bq27xxx from w1 to power/supply (2017-07-25 15:17:39 +0200)
Greg, should it be pulled into your tree or submitted as a separate pull request or as set of patches?
Either way looks good to me, please get it into your tree.
next prev parent reply other threads:[~2017-08-27 7:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-19 17:04 [PATCH v2 0/2] Remove BQ27xxx platform interface Andrew F. Davis
2017-07-19 17:04 ` [PATCH v2 1/2] power: supply: move HDQ interface for bq27xxx from w1 to power/supply Andrew F. Davis
2017-07-25 13:30 ` Sebastian Reichel
2017-07-25 13:48 ` Sebastian Reichel
2017-08-27 7:25 ` Evgeniy Polyakov [this message]
2017-07-19 17:04 ` [PATCH v2 2/2] power: supply: bq27xxx: move platform driver code into bq27xxx_battery_hdq.c Andrew F. Davis
2017-07-25 13:42 ` 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=1195431503818734@web4g.yandex.ru \
--to=zbr@ioremap.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=sebastian.reichel@collabora.co.uk \
/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