From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752451AbcLSAHh (ORCPT ); Sun, 18 Dec 2016 19:07:37 -0500 Received: from mx1.redhat.com ([209.132.183.28]:32906 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751171AbcLSAHg (ORCPT ); Sun, 18 Dec 2016 19:07:36 -0500 From: Hans de Goede To: Sebastian Reichel , Chen-Yu Tsai , MyungJoo Ham , Chanwoo Choi Cc: "russianneuromancer @ ya . ru" , linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH 00/14] extcon api extension + axp288_charger fixes Date: Mon, 19 Dec 2016 01:07:17 +0100 Message-Id: <20161219000731.10188-1-hdegoede@redhat.com> X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.27]); Mon, 19 Dec 2016 00:07:35 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi extcon and power-supply system maintainers, This series really are 2 separate series, patches 1 - 2 add a new extcon_get_extcon_dev_by_cable_id function to the extcon core. Patches 3 - 15 consist of various fixes for the axp288_charger driver, including one fix which uses the new extcon_get_extcon_dev_by_cable_id making this series depend on the extcon patches. So we will need some coordination between the merging of these 2 series. Since the extcon patches are quite simple, perhaps they can still be merged into 4.10 ? Otherwise the extcon maintainers will need to provide a stable branch with these 2 patches which the power-supply maintainer can merge into power-supply/next . Regards, Hans