diff for duplicates of <56FA99D0.1010004@nvidia.com> diff --git a/a/1.txt b/N1/1.txt index 8f62d3f..155b663 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -64,7 +64,7 @@ On 3/28/2016 9:52 PM, YH Huang wrote: >>>> And there are some words about FULLY_DISCHARGED. >>>> "Discharge should be stopped soon." >>>> "This status bit may be set prior to the ->>>> ‘TERMINATE_DISCHARGE_ALARM’ as an early or first level warning of end of +>>>> ?TERMINATE_DISCHARGE_ALARM? as an early or first level warning of end of >>>> battery charge." >>>> It looks like the FULLY_DISCHARGED status is used to announce the >>>> warning of battery charge and it is still discharging if there is no one @@ -96,7 +96,7 @@ high->low: DISCHARGING ->~20%: FULLY_DISCHARGED >~20%: <nothing> = charging -From this understanding, it seems like we can't expect FULLY_DISCHARGED +>From this understanding, it seems like we can't expect FULLY_DISCHARGED to ever be the only flag, nor can we expect it to go away when the system is initially plugged in. In light of this, I can see why your patch is preferable to the existing code, as the existing code could diff --git a/a/content_digest b/N1/content_digest index 27beecb..91d6a68 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -6,19 +6,10 @@ "ref\0CAGS+omBVStB3mfXtDHdbsOK+y2UesGYtZBtYm=ctcpBfm88VEg@mail.gmail.com\0" "ref\056F95451.5040607@nvidia.com\0" "ref\01459216353.16645.20.camel@mtksdaap41\0" - "From\0Rhyland Klein <rklein@nvidia.com>\0" - "Subject\0Re: [PATCH] sbs-battery: fix power status when battery is dry\0" + "From\0rklein@nvidia.com (Rhyland Klein)\0" + "Subject\0[PATCH] sbs-battery: fix power status when battery is dry\0" "Date\0Tue, 29 Mar 2016 11:05:52 -0400\0" - "To\0YH Huang <yh.huang@mediatek.com>\0" - "Cc\0Daniel Kurtz <djkurtz@chromium.org>" - linux-pm@vger.kernel.org - Dmitry Eremin-Solenikov <dbaryshkov@gmail.com> - Sebastian Reichel <sre@kernel.org> - linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org> - moderated list:ARM/Mediatek SoC support <linux-mediatek@lists.infradead.org> - Matthias Brugger <matthias.bgg@gmail.com> - David Woodhouse <dwmw2@infradead.org> - " linux-arm-kernel@lists.infradead.org <linux-arm-kernel@lists.infradead.org>\0" + "To\0linux-arm-kernel@lists.infradead.org\0" "\00:1\0" "b\0" "On 3/28/2016 9:52 PM, YH Huang wrote:\n" @@ -87,7 +78,7 @@ ">>>> And there are some words about FULLY_DISCHARGED.\n" ">>>> \"Discharge should be stopped soon.\"\n" ">>>> \"This status bit may be set prior to the\n" - ">>>> \342\200\230TERMINATE_DISCHARGE_ALARM\342\200\231 as an early or first level warning of end of\n" + ">>>> ?TERMINATE_DISCHARGE_ALARM? as an early or first level warning of end of\n" ">>>> battery charge.\"\n" ">>>> It looks like the FULLY_DISCHARGED status is used to announce the\n" ">>>> warning of battery charge and it is still discharging if there is no one\n" @@ -119,7 +110,7 @@ "->~20%: FULLY_DISCHARGED\n" ">~20%: <nothing> = charging\n" "\n" - "From this understanding, it seems like we can't expect FULLY_DISCHARGED\n" + ">From this understanding, it seems like we can't expect FULLY_DISCHARGED\n" "to ever be the only flag, nor can we expect it to go away when the\n" "system is initially plugged in. In light of this, I can see why your\n" "patch is preferable to the existing code, as the existing code could\n" @@ -139,4 +130,4 @@ "-- \n" nvpublic -ecae71d695b0f5999142cbb8db8d33642f866b18638ad38703e11ea380e0a120 +056b8e01ec415172de4c32cacb5c57158d3a6a5100ba502a7de5b2de3c2a7b0a
diff --git a/a/1.txt b/N2/1.txt index 8f62d3f..9ac97f2 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -96,7 +96,7 @@ high->low: DISCHARGING ->~20%: FULLY_DISCHARGED >~20%: <nothing> = charging -From this understanding, it seems like we can't expect FULLY_DISCHARGED +>From this understanding, it seems like we can't expect FULLY_DISCHARGED to ever be the only flag, nor can we expect it to go away when the system is initially plugged in. In light of this, I can see why your patch is preferable to the existing code, as the existing code could diff --git a/a/content_digest b/N2/content_digest index 27beecb..1a68786 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -11,7 +11,7 @@ "Date\0Tue, 29 Mar 2016 11:05:52 -0400\0" "To\0YH Huang <yh.huang@mediatek.com>\0" "Cc\0Daniel Kurtz <djkurtz@chromium.org>" - linux-pm@vger.kernel.org + <linux-pm@vger.kernel.org> Dmitry Eremin-Solenikov <dbaryshkov@gmail.com> Sebastian Reichel <sre@kernel.org> linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org> @@ -119,7 +119,7 @@ "->~20%: FULLY_DISCHARGED\n" ">~20%: <nothing> = charging\n" "\n" - "From this understanding, it seems like we can't expect FULLY_DISCHARGED\n" + ">From this understanding, it seems like we can't expect FULLY_DISCHARGED\n" "to ever be the only flag, nor can we expect it to go away when the\n" "system is initially plugged in. In light of this, I can see why your\n" "patch is preferable to the existing code, as the existing code could\n" @@ -139,4 +139,4 @@ "-- \n" nvpublic -ecae71d695b0f5999142cbb8db8d33642f866b18638ad38703e11ea380e0a120 +f7d7b3ac8d8e483f29bfe73d88a8bda6aba50c54e9efc8342f23d221ed7b7777
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.