Lines Matching full:cases

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