From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 73DD2C5517A for ; Wed, 21 Oct 2020 04:51:55 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 2556922248 for ; Wed, 21 Oct 2020 04:51:55 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2440264AbgJUEvy (ORCPT ); Wed, 21 Oct 2020 00:51:54 -0400 Received: from muru.com ([72.249.23.125]:46352 "EHLO muru.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2440263AbgJUEvy (ORCPT ); Wed, 21 Oct 2020 00:51:54 -0400 Received: from atomide.com (localhost [127.0.0.1]) by muru.com (Postfix) with ESMTPS id C558880B0; Wed, 21 Oct 2020 04:51:57 +0000 (UTC) Date: Wed, 21 Oct 2020 07:51:45 +0300 From: Tony Lindgren To: Sebastian Reichel Cc: Dev Null , linux-omap@vger.kernel.org, linux-pm@vger.kernel.org Subject: Re: [PATCH 1/1] power: supply: cpcap-battery: improve handling of 3rd party and XT875 batteries. Message-ID: <20201021045145.GA5974@atomide.com> References: <20201020225312.b4ea29c9dc3ae00f23e39280@uvos.xyz> <20201020214126.tkf37xpehnpxli4a@earth.universe> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20201020214126.tkf37xpehnpxli4a@earth.universe> Precedence: bulk List-ID: X-Mailing-List: linux-omap@vger.kernel.org Hi, * Sebastian Reichel [201020 21:41]: > The context of this patch is not available in cpcap-battery driver > from mainline. So this has dependencies on other patches, which > need to be submitted first. I currently do not have any pending > cpcap patches, but IIRC there was a big patchset which had to be > resubmitted. Yes this $subject patch as a split up series should be based on the mainline kernel, and not on the WIP battery capacity patches. I doubt there will be any severe rebase issues for the capacity patches. FYI, I'm slowly working on the battery capacity series but still need to decouple the battrery full status from charge current as that won't work for cases where we have CPU load :) We just need to set the status based on charger full interrupt. Regards, Tony