Searched refs:cases (Results 226 – 248 of 248) sorted by relevance
12345678910
577 * Fixed bus error after network disconnection that happened in some cases.1014 * Refactored HTTP server sample to better demonstrate server use cases.
988 * :github:`28206` - mimxrt685_cm33: many cases has no console output seems hangs in kernel init.1059 * :github:`28000` - sam_e70_xplained:Test cases run failed at tests/net/lib/dns_packet/.1089 * :github:`27821` - frdm_k64f:running test cases /tests/subsys/power/power_mgmt/ error
1089 * :github:`23907` - Shell overdo argument parsing in some cases1436 * :github:`6648` - Trusted Execution Framework: practical use-cases (high-level overview)
880 on the total retransmission timeout (as in other cases) making the config
498 amount of test cases in existing tests to increase code coverage.1260 * :github:`15446` - ssanitycheck --coverage -p mps2_an385: Some remaing test cases that are still f…
1089 * Wrapper around p4wq (rtio workq) created to go from blocking to non-blocking behavior in cases1454 * Added receive callback for dummy L2, applicable in certain use cases
409 * :github:`9061` - sanitycheck not printing QEMU console in some cases
1740 … kernel.scheduler.multiq: Failed since #35276 ("cooperative scheduling only" special cases removal)1907 * :github:`25832` - [test][kernel][lpcxpresso55s69_ns] kernel cases meet ESF could not be retrieved…
1190 * Fixed double TCP context dereferencing in certain corner cases.
885 by L2 in certain cases.
513 only a certain set of features is required and 8 MPU regions are, in many cases, sufficient.
684 In all three cases, the certification scheme (e.g., FIPS 140-2 [NIST02]_
198 while being a HW agnostic test platform which in some cases utilizes the host
390 # be prevented in individual cases by putting a % sign in front of the word or739 # accept a match between prototype and implementation in such cases.2778 # So in most cases it will be better to enable call graphs for selected2790 # So in most cases it will be better to enable caller graphs for selected
573 run in interrupt context. Only useful for test cases that need
770 handful of workaround cases in the kernel that need to be
589 This would enable cases where an attacker could copy the peer device
1099 This will prolong the connection event to from being closed in cases
35 Additionally, in some cases modules (particularly vendor HALs) can contain
623 is necessary to avoid some pathological edge cases.)
3232 # This is needed to properly handle cases where we want to check value against5052 # but in cases a section shall only be present at a specific
507 Client model targets the new node. In most common use-cases, the Configuration Client is depending
301 …ation) and after training (referred to as testing) It's important in both cases that we use fresh …
