Lines Matching full:cases

84 from the current review queue. Likewise for cases where patches would
203 at the end of the week. In some cases pull requests could additionally
222 Q: Verifier changes and test cases
224 Q: I made a BPF verifier change, do I need to add test cases for
228 it is absolutely necessary to add test cases to the BPF kernel
233 cases, including a lot of corner cases that LLVM BPF back end may
234 generate out of the restricted C code. Thus, adding test cases is
236 affect prior use-cases. Thus, treat those test cases as: verifier
249 The more test cases we add to BPF selftests, the better the coverage
316 commit is in net-next (or in some cases bpf-next). The ``Fixes:`` tag is
351 Also always make sure to add BPF test cases (e.g. test_bpf.c and
452 test cases and are constantly updated with new BPF test sequences, or
464 so for the majority of use-cases it is not required to compile LLVM by
575 Q: In some cases clang flag ``-target bpf`` is used but in other cases the
585   understand these assembly codes, which is true in most cases.