5fb929032de14ca78163e1d0c42c34f6fb287da4 - platform/frameworks/base

commit	5fb929032de14ca78163e1d0c42c34f6fb287da4	[log] [tgz]
author	Jonathan Basseri <misterikkit@google.com>	Thu Nov 16 10:58:01 2017 -0800
committer	Nathan Harold <nharold@google.com>	Tue Dec 12 13:50:35 2017 -0800
tree	5efce3a17f03238572ddc890a872ea3610be45c7
parent	403c8f72e38114d0aadfd852b98b323827068e5b [diff]

Use consistent naming for allocating SPI.

Throughout the IPsec code (API, system server, netd) we use "reserve"
SPI and "allocate" SPI interchangeably. This renames to use "allocate"
everywhere for self-consistency and consistency with the kernel
(ALLOCSPI).

In javadoc, I am leaving the word "reserve" in several places because it
is still an accurate description of how the method behaves.

Bug: 69128142
Test: TreeHugger should be enough
Change-Id: I8ea603b4612303b0393beef04032671fa53d2106

api/current.txt[diff]
core/java/android/net/IIpSecService.aidl[diff]
core/java/android/net/IpSecManager.java[diff]
core/java/android/net/IpSecTransform.java[diff]
services/core/java/com/android/server/IpSecService.java[diff]
tests/net/java/android/net/IpSecManagerTest.java[diff]
tests/net/java/com/android/server/IpSecServiceParameterizedTest.java[diff]
tests/net/java/com/android/server/IpSecServiceTest.java[diff]

8 files changed

tree: 5efce3a17f03238572ddc890a872ea3610be45c7