Searched refs:removing (Results 1 – 20 of 20) sorted by relevance
19 // TODO: Delete this file. It's no longer needed, but removing it on udc-dev will cause
31 * next PT_LOAD segment from mapping over .plt section removing
26 // Please consider removing redundant or irrelevant files from 'license_text:'.
7 … description: "Feature flag for refactoring InsetsController and removing ImeInsetsSourceConsumer"
7 description: "This flag controls removing expired notification bitmaps"
220 "removing unused section from '%0' in file '%1'",221 "removing unused section from '%0' in file '%1'")
36 `ChipInfo`. `MediaTttChipControllerCommon` has all the common logic for adding and removing the
34 // 10208 is reserved due to removing the old atom.
130 // removing additional bits --> unit8
29 * 2. Never reuse a proto field number. When removing a field, mark it as reserved.
132 // Putting/removing handlers from the map
51 # Referenced via CarServiceHelperService in car-frameworks-service (avoid removing)
141 result_message_brief_banned_word = Consider removing inappropriate words from this item\'s text143 …text = This item may use %1$s font for a long passage of text. Consider removing the style from th…144 result_message_brief_styled_text = Consider removing %1$s styling on longer passages of text.
1115 SparseArray<AuthorityInfo> removing = new SparseArray<AuthorityInfo>(); in removeStaleAccounts() local1129 removing.put(auth.ident, auth); in removeStaleAccounts()1136 int i = removing.size(); in removeStaleAccounts()1140 int ident = removing.keyAt(i); in removeStaleAccounts()1141 AuthorityInfo auth = removing.valueAt(i); in removeStaleAccounts()
433 including removing the callbacks and making sure that the backends remove themselves from the
264 // Consider removing this if it becomes a problem1484 // 10208 is reserved due to removing the old atom.1511 * - These form an API, so renaming, renumbering or removing fields is
4 # If you are changing/removing APIs listed in this file, you do not need to