archives/pebble
2
0
Fork 0
mirror of https://github.com/google/pebble.git synced 2025-04-30 15:21:41 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

spelling: implicitly

Browse source 
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
This commit is contained in:
Josh Soref 2025-01-28 14:48:44 -05:00
parent fdc40c6e40
commit 8ce07c9151
2 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
src/fw/comm/ble/gap_le_slave_discovery.h
View file

@ -21,7 +21,7 @@
//! discovery purposes. The advertisement will contain the device name, //! discovery purposes. The advertisement will contain the device name,
//! transmit power level (to be able to order devices by estimated proximity), //! transmit power level (to be able to order devices by estimated proximity),
//! Pebble Service UUID and discoverability flags. //! Pebble Service UUID and discoverability flags.
//! Advertising devices will implicitely become the slave when being connected //! Advertising devices will implicitly become the slave when being connected
//! to, so the "slave" part in the file name is redundant, but kept for //! to, so the "slave" part in the file name is redundant, but kept for
//! the sake of completeness. //! the sake of completeness.

2
waftools/emscripten.py
View file

@ -159,7 +159,7 @@ def process_emscripten_cprogram_link_args(self):
for s in get_rule_and_env_values('emx_other_settings'): for s in get_rule_and_env_values('emx_other_settings'):
add_emcc_settings('-s', s) add_emcc_settings('-s', s)
# Emscripten implicitely regenerates caches (libc.bc, dlmalloc.bc, # Emscripten implicitly regenerates caches (libc.bc, dlmalloc.bc,
# struct_info.compiled.json and optimizer.exe) as needed. # struct_info.compiled.json and optimizer.exe) as needed.
# When running multiple instantiations of emcc in parallel, this is # When running multiple instantiations of emcc in parallel, this is
# problematic because they will each race to generate the caches, # problematic because they will each race to generate the caches,