Home
last modified time | relevance | path

Searched full:rule (Results 1 – 25 of 111) sorted by relevance

12345

/Zephyr-latest/include/zephyr/net/
Dnet_pkt_filter.h49 /** @brief filter rule structure */
51 sys_snode_t node; /**< Slist rule list node */
53 uint32_t nb_tests; /**< number of tests for this rule */
57 /** @brief Default rule list termination for accepting a packet */
59 /** @brief Default rule list termination for rejecting a packet */
62 /** @brief rule set for a given test location */
68 /** @brief rule list applied to outgoing packets */
70 /** @brief rule list applied to incoming packets */
72 /** @brief rule list applied for local incoming packets */
74 /** @brief rule list applied for IPv4 incoming packets */
[all …]
/Zephyr-latest/doc/connectivity/networking/api/
Dnet_pkt_filter.rst22 Each rule is made of a set of conditions and a packet outcome. Every packet
23 is subjected to the conditions attached to a rule. When all the conditions
24 for a given rule are true then the packet outcome is immediately determined
25 as specified by the current rule and no more rules are considered. If one
26 condition is false then the next rule in the list is considered.
31 A rule is represented by a :c:struct:`npf_rule` object. It can be inserted to,
32 appended to or removed from a rule list contained in a
35 Currently, two such rule lists exist: ``npf_send_rules`` for outgoing packets,
38 If a filter rule list is empty then ``NET_OK`` is assumed. If a non-empty
39 rule list runs to the end then ``NET_DROP`` is assumed. However it is
[all …]
/Zephyr-latest/boards/nordic/nrf52840dongle/doc/img/
DnRF52840_dongle_press_reset.svg239 …<polyline fill-rule="evenodd" clip-rule="evenodd" points="201.57,151.47 200.67,152.25 200.67,157.4…
242 …<polyline fill-rule="evenodd" clip-rule="evenodd" points="201.15,151.29 201.03,151.29 200.91,151.3…
245 …<polyline fill-rule="evenodd" clip-rule="evenodd" points="205.53,157.53 205.53,157.83 205.47,158.0…
249 …<polyline fill-rule="evenodd" clip-rule="evenodd" points="209.73,151.47 208.83,152.25 208.83,157.4…
252 …<polyline fill-rule="evenodd" clip-rule="evenodd" points="209.31,151.29 209.19,151.29 209.07,151.3…
255 …<path fill-rule="evenodd" clip-rule="evenodd" d="M212.85,151.89l-0.24,0.36l-0.06,0.06c-0.249,0.514…
260 …<path fill-rule="evenodd" clip-rule="evenodd" d="M214.47,151.23l-0.12,0.06c-0.505-0.055-0.977,0.13…
265 …<polyline fill-rule="evenodd" clip-rule="evenodd" points="230.55,151.47 229.65,152.25 229.65,157.4…
268 …<polyline fill-rule="evenodd" clip-rule="evenodd" points="230.13,151.29 230.01,151.29 229.89,151.3…
271 …<polyline fill-rule="evenodd" clip-rule="evenodd" points="234.51,157.53 234.51,157.83 234.45,158.0…
[all …]
/Zephyr-latest/subsys/net/pkt_filter/
Dbase.c15 * Our actual rule lists for supported test points
73 * Rule application
80 static bool apply_tests(struct npf_rule *rule, struct net_pkt *pkt) in apply_tests() argument
86 for (i = 0; i < rule->nb_tests; i++) { in apply_tests()
87 test = rule->tests[i]; in apply_tests()
99 * We return the specified result for the first rule whose tests are all true.
103 struct npf_rule *rule; in evaluate() local
112 SYS_SLIST_FOR_EACH_CONTAINER(rule_head, rule, node) { in evaluate()
113 if (apply_tests(rule, pkt) == true) { in evaluate()
114 return rule->result; in evaluate()
[all …]
/Zephyr-latest/doc/contribute/coding_guidelines/
Dindex.rst64 * - Zephyr rule
66 - MISRA-C 2012 rule
186 …- `Rule 1.2 <https://gitlab.com/MISRA/MISRA-C/MISRA-C-2012/Example-Suite/-/blob/master/R_01_02.c>…
193 …- `Rule 1.3 <https://gitlab.com/MISRA/MISRA-C/MISRA-C-2012/Example-Suite/-/blob/master/R_01_03.c>…
200 …- | `Rule 2.1 example 1 <https://gitlab.com/MISRA/MISRA-C/MISRA-C-2012/Example-Suite/-/blob/maste…
201 …| `Rule 2.1 example 2 <https://gitlab.com/MISRA/MISRA-C/MISRA-C-2012/Example-Suite/-/blob/master/R…
208 …- `Rule 2.2 <https://gitlab.com/MISRA/MISRA-C/MISRA-C-2012/Example-Suite/-/blob/master/R_02_02.c>…
215 …- `Rule 2.3 <https://gitlab.com/MISRA/MISRA-C/MISRA-C-2012/Example-Suite/-/blob/master/R_02_03.c>…
222 …- `Rule 2.6 <https://gitlab.com/MISRA/MISRA-C/MISRA-C-2012/Example-Suite/-/blob/master/R_02_06.c>…
229 …- `Rule 2.7 <https://gitlab.com/MISRA/MISRA-C/MISRA-C-2012/Example-Suite/-/blob/master/R_02_07.c>…
[all …]
/Zephyr-latest/scripts/gitlint/
Dzephyr_commit_rules.py8 A CommitRule contrasts with a LineRule (see examples/my_line_rules.py) in that a commit rule is onl…
21 # A rule MUST have a human friendly name
24 # A rule MUST have an *unique* id, we recommend starting with UC (for User-defined Commit-rule).
27 # A rule MAY have an options_spec if its behavior should be configurable.
39 # A rule MUST have a human friendly name
42 # A rule MUST have an *unique* id, we recommend starting with UC (for User-defined Commit-rule).
45 # A rule MAY have an options_spec if its behavior should be configurable.
56 """ This rule will enforce that each commit contains a "Signed-off-by" line.
60 # A rule MUST have a human friendly name
63 # A rule MUST have an *unique* id, we recommend starting with UC (for User-defined Commit-rule).
/Zephyr-latest/scripts/coccinelle/
Dsame_identifier.cocci1 // Check violations for rule 5.7
32 msg = "WARNING: Violation to rule 5.7 (Tag name should be unique) tag: {}".format(v)
53 msg = "WARNING: Violation to rule 5.7 (Tag name should be unique) tag: {}".format(v)
74 msg = "WARNING: Violation to rule 5.7 (Tag name should be unique) tag: {}".format(v)
Dboolean.cocci1 // Check violations for rule 14.4
49 msg = "WARNING: Violation to rule 14.4 (Controlling expression shall have essentially Boolean type)"
78 msg = "WARNING: Violation to rule 14.4 (Controlling expression shall have essentially Boolean type)"
99 msg = "WARNING: Violation to rule 14.4 (Controlling expression shall have essentially Boolean type)"
Dreserved_names.cocci1 // Check violations for rule 5.7
47 msg = "WARNING: Violation to rule 21.2 (Should not used a reserved identifier) - {}".format(v)
66 msg = "WARNING: Violation to rule 21.2 (Should not used a reserved identifier) - {}".format(v)
88 msg = "WARNING: Violation to rule 21.2 (Should not used a reserved identifier) - {}".format(v)
Didentifier_length.cocci29 …msg="WARNING: Violation to rule 5.1 or 5.2 (Identifiers shall be distinct) %s length %d > 31" % (i…
/Zephyr-latest/scripts/utils/
Dconvert_guidelines.py9 Or simply use the rule list to generate a filter to suppress all other rules
40 print('Rule ' + guideline_number + ' ' + severity, file=outputfile)
43 print(description + '(Misra rule ' + guideline_number + ')', file=outputfile)
71 # Each Rule is a new table column so start with '[tab]* - Rule'
73 pattern_new_line = re.compile(r'^ \* - Rule ([0-9]+.[0-9]+).*$')
/Zephyr-latest/subsys/testsuite/ztest/
DKconfig124 This rule will call z_test_1cpu_start before each unit test and
133 This rule will fail the project if not all tests have been run.
140 This rule will reset gcov counters before running tests. This ensures
149 This rule will shuffle the order of tests and test suites.
171 This rule will repeat the tests and the test suites.
178 This rule will execute a test suite N number of times.
184 This rule will execute a test N number of times.
/Zephyr-latest/doc/hardware/peripherals/
Dflash.rst12 the flash memory beginning address. This rule shall be applied to
16 An exception from the rule may be applied to a vendor-specific flash
/Zephyr-latest/doc/_static/latex/
Dtitle.tex20 \color{bg-color} \rule{2cm}{1.7cm}
39 \color{bg-color} \rule{1.5cm}{1.3cm}
/Zephyr-latest/
D.gitlint52 # Whether to ignore this rule on merge commits (which typically only have a title)
59 # By specifying this rule, developers can only change the file when they explicitly reference
/Zephyr-latest/doc/kernel/services/smp/
Dsmpinit.svg31 …style="fill:#000000;fill-opacity:1;fill-rule:evenodd;stroke:#000000;stroke-width:1.00000003pt;stro…
46 …style="fill:#000000;fill-opacity:1;fill-rule:evenodd;stroke:#000000;stroke-width:1.00000003pt;stro…
63 …style="fill:#000000;fill-opacity:1;fill-rule:evenodd;stroke:#000000;stroke-width:1.00000003pt;stro…
77 …style="fill:#000000;fill-opacity:1;fill-rule:evenodd;stroke:#000000;stroke-width:1.00000003pt;stro…
94 …style="fill:#000000;fill-opacity:1;fill-rule:evenodd;stroke:#000000;stroke-width:1.00000003pt;stro…
110 …style="fill:#000000;fill-opacity:1;fill-rule:evenodd;stroke:#000000;stroke-width:1.00000003pt;stro…
125 …style="fill:#000000;fill-opacity:1;fill-rule:evenodd;stroke:#000000;stroke-width:1.00000003pt;stro…
141 …style="fill:#000000;fill-opacity:1;fill-rule:evenodd;stroke:#000000;stroke-width:1.00000003pt;stro…
156 …style="fill:#000000;fill-opacity:1;fill-rule:evenodd;stroke:#000000;stroke-width:1.00000003pt;stro…
171 …style="fill:#000000;fill-opacity:1;fill-rule:evenodd;stroke:#000000;stroke-width:1.00000003pt;stro…
/Zephyr-latest/cmake/sca/eclair/ECL/
Dadopted_deviations.ecl32 …er. For the ones with internal linkage the use of the extern qualifier is a violation of rule 8.8."
42 …Chainging the generators could be dangerous and the advantages in enforcing the rule do not outwei…
/Zephyr-latest/doc/build/dts/
Dbindings-upstream.rst26 In particular, this rule applies if:
101 this rule is if you are replicating a well-established binding from somewhere
120 actual vendor. There are some exceptions to this rule, but the practice is
135 kernel's equivalent file; this process is exempt from the previous rule.
/Zephyr-latest/tests/net/npf/src/
Dmain.c141 /* remove first iface rule */ in test_npf_iface()
147 /* test with only default drop rule in place */ in test_npf_iface()
151 /* insert second iface rule */ in test_npf_iface()
154 /* test with new rule in place */ in test_npf_iface()
317 /* test standard match rule from previous test */ in test_npf_eth_mac_addr_mask()
326 /* insert masked address match rule */ in test_npf_eth_mac_addr_mask()
/Zephyr-latest/subsys/testsuite/ztest/include/zephyr/
Dztest_test.h518 * @brief Test rule callback function signature
520 * The function signature that can be used to register a test rule's before/after callback. This
535 * @brief Define a test rule that will run before/after each unit test.
543 * - Test rule's `before` function will run before the suite's `before` function. This is done to
544 * allow the test suite's customization to take precedence over the rule which is applied to all
546 * - Test rule's `after` function is not guaranteed to run in any particular order.
548 * @param name The name for the test rule (must be unique within the compilation unit)
/Zephyr-latest/scripts/schemas/twister/
Dplatform-schema.yaml17 matching-rule: "any"
/Zephyr-latest/tests/bsim/bluetooth/host/misc/sample_test/
DCMakeLists.txt34 # As a general rule of thumb: All functions that use `TEST_ASSERT()` are part of
/Zephyr-latest/drivers/ieee802154/
Dieee802154_cc13xx_cc26xx.c342 drv_data->cmd_ieee_tx.condition.rule = in ieee802154_cc13xx_cc26xx_tx()
627 drv_data->cmd_fs.condition.rule = COND_NEVER; in ieee802154_cc13xx_cc26xx_init()
656 .condition.rule = COND_NEVER,
729 .condition.rule = COND_STOP_ON_FALSE,
754 .condition.rule = COND_NEVER,
772 .condition.rule = COND_NEVER,
794 .condition.rule = COND_NEVER,
/Zephyr-latest/doc/kernel/data_structures/
Drbtree.rst78 each node, either red or black, and enforcing a rule that no red child
81 that number of "extra" red nodes may be present). This rule is
/Zephyr-latest/tests/ztest/base/src/
Dmain.c93 * Sample rule tests
152 * Normally, we wouldn't assert here, but it's the only way to test that the rule's in rule_test_teardown()

12345