Home
last modified time | relevance | path

Searched refs:bad (Results 1 – 25 of 28) sorted by relevance

12

/Zephyr-latest/scripts/ci/
Dpylintrc71 bad-classmethod-argument,
72 bad-mcs-method-argument,
73 bad-mcs-classmethod-argument,
94 bad-reversed-sequence,
122 bad-except-order,
123 raising-bad-type,
124 bad-exception-context,
129 bad-super-call,
156 bad-format-character,
163 bad-string-format-type,
[all …]
/Zephyr-latest/tests/bsim/bluetooth/host/att/pipeline/dut/src/
Dmain.c296 struct bt_conn *good, *bad; in dut_procedure() local
306 bad = connect(); in dut_procedure()
310 do_dlu(bad); in dut_procedure()
311 send_write_handle(bad); in dut_procedure()
/Zephyr-latest/scripts/coccinelle/
Dderef_null.cocci84 E->f@p // bad use
145 E->f@p // bad use
205 * E->f@p // bad use
278 * E->f@p // bad use
/Zephyr-latest/tests/drivers/sdhc/
DREADME.txt10 the reset left the SDHC in a bad state subsequent tests may fail.
/Zephyr-latest/subsys/fs/nvs/
DKconfig41 bool "Non-volatile Storage bad memory region recovery"
/Zephyr-latest/drivers/watchdog/
DKconfig.nxp_fs2641 there is a bad watchdog refresh, this counter is reset to 0.
/Zephyr-latest/scripts/pylib/twister/twisterlib/
Dtestinstance.py406 fns = [x for x in fns if not any(bad in os.path.basename(x) for bad in blocklist)]
/Zephyr-latest/doc/releases/
Drelease-notes-1.9.rst285 * ``ZEP-2329`` - bad memory access tests/net/route
286 * ``ZEP-2330`` - bad memory access tests/net/rpl
287 * ``ZEP-2331`` - bad memory access tests/net/ieee802154/l2
288 * ``ZEP-2332`` - bad memory access tests/net/ip-addr
Drelease-notes-2.1.rst760 * :github:`19165` - zephyr\_file generates bad links on branches
938 * :github:`652` - Provide a mean to find tests with 0 platforms due to bad filtering
Drelease-notes-1.7.rst304 * ``ZEP-1419`` - SYS_LOG macros cause potentially bad behavior due to printk/printf selection
Drelease-notes-1.11.rst265 * :github:`3838` - Some tests end up with 0 platforms due to bad filtering
Drelease-notes-1.10.rst258 * :github:`2202` - sporadic bad RAM pointer error under qemu_nios2
Drelease-notes-1.14.rst128 * :github:`16411` - bad regex for west version check in host-tools.cmake
222 * :github:`19165` - zephyr_file generates bad links on branches
327 * :github:`16411` - bad regex for west version check in host-tools.cmake
429 * :github:`19165` - zephyr_file generates bad links on branches
Drelease-notes-1.12.rst542 * :github:`6973` - bad magic number in 'kconfiglib' error when generating docs
Drelease-notes-2.6.rst1271 * :github:`35051` - CONFIG_LOG2 fails for floating point output with warning and bad output
1615 * :github:`33505` - WS2812 SPI LED driver with DMA on nrf52 bad SPI data
Drelease-notes-3.2.rst251 * Fixed issue with incorrect ``ssf`` under bad syscall.
2026 * :github:`49162` - Calling cache maintenance APIs from user mode threads result in a bad syscall e…
Drelease-notes-2.3.rst867 * :github:`25233` - bad logic in test_busy_wait of tests/kernel/context
/Zephyr-latest/doc/build/dts/
Dbindings-intro.rst71 bad-node {
/Zephyr-latest/subsys/bluetooth/controller/
DKconfig.df149 bool "Sampling of CTE for PDUs with bad CRC"
153 Enable support for sampling of CTE for PDUs that have bad CRC.
/Zephyr-latest/samples/sensor/bme280/
DREADME.rst137 [00:00:00.379,821] <dbg> BME280.bme280_init: bad chip id 0xff
/Zephyr-latest/doc/develop/west/
Dwest-apis.rst279 configuration. This has proven to be a bad design decision since west's APIs
Drelease-notes.rst209 - West commands that were run with a bad local configuration file dumped stack
/Zephyr-latest/doc/security/
Dsecure-coding.rst182 values), not blacklists (which attempt to list known-bad values)).
/Zephyr-latest/doc/kernel/usermode/
Dsyscalls.rst579 of reasons: missing driver API, bad kernel object pointer, wrong kernel
621 when bad parameters are passed in as they do not propagate errors.
/Zephyr-latest/boards/native/doc/
Darch_soc.rst154 Note that busy wait loops are in general a bad coding practice as they

12