From: Sebastian Reichel <sre@kernel.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Chen-Yu Tsai <wens@csie.org>,
"russianneuromancer @ ya . ru" <russianneuromancer@ya.ru>,
linux-pm@vger.kernel.org
Subject: Re: [PATCH 0/1] power: supply: axp288_charger: Use one notifier_block per extcon cable
Date: Fri, 23 Dec 2016 02:37:58 +0100 [thread overview]
Message-ID: <20161223013757.75spgjgki7foglba@earth> (raw)
In-Reply-To: <20161221172823.14406-1-hdegoede@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 215 bytes --]
Hi,
On Wed, Dec 21, 2016 at 06:28:22PM +0100, Hans de Goede wrote:
> Here is one more axp288_charger fix, note this applies on top of
> v2 of my previous axp288_charger fixes series.
Thanks, queued.
-- Sebastian
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2016-12-23 1:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-21 17:28 [PATCH 0/1] power: supply: axp288_charger: Use one notifier_block per extcon cable Hans de Goede
2016-12-21 17:28 ` [PATCH] " Hans de Goede
2016-12-23 1:37 ` Sebastian Reichel [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=20161223013757.75spgjgki7foglba@earth \
--to=sre@kernel.org \
--cc=hdegoede@redhat.com \
--cc=linux-pm@vger.kernel.org \
--cc=russianneuromancer@ya.ru \
--cc=wens@csie.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