From 0dab2bf10ab5db6a16411dc699e278c4c5ab5d82 Mon Sep 17 00:00:00 2001 From: junyulai Date: Fri, 29 Jan 2021 14:55:35 +0800 Subject: [PATCH] Address leftover comments on aosp/1212191 Test: TH Bug: 149467454 Change-Id: Id19456693c0b4173cc4065463c037f01733c7a56 --- tetheroffload/control/1.1/IOffloadControl.hal | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/tetheroffload/control/1.1/IOffloadControl.hal b/tetheroffload/control/1.1/IOffloadControl.hal index eb5b8a1383..2eb54c81c8 100644 --- a/tetheroffload/control/1.1/IOffloadControl.hal +++ b/tetheroffload/control/1.1/IOffloadControl.hal @@ -37,11 +37,9 @@ interface IOffloadControl extends @1.0::IOffloadControl { * offload is started. This is because the quota values would likely become stale over * time and would not reflect any new traffic that has occurred. * - * This API replaces {@link @1.0::IOffloadControl::setDataLimit}, the framework would always - * calls this API if 1.1 HAL is supported. Otherwise, calls the other one. Thus, no - * interaction between the two APIs need to be addressed. However, the hardware implementation - * still needs to keep functionality of both in case of shipping with older framework that - * doesn't support 1.1 HAL. + * This API replaces {@link @1.0::IOffloadControl::setDataLimit}, the framework will always + * call setDataWarningAndLimit on 1.1 implementations, and setDataLimit on 1.0 implementations. + * Thus, no interaction between the two APIs need to be addressed. * * The specified quota bytes MUST replace any previous quotas set by * {@code setDataWarningAndLimit} specified on the same interface. It may be interpreted as