| /openbmc/phosphor-gpio-monitor/ |
| H A D | meson.build | 74 'rules.d',
78 '99-gpio-keys.rules',
|
| /openbmc/sdbusplus/test/async/ |
| H A D | context.cpp | 104 *ctx, sdbusplus::bus::match::rules::interfacesAdded( in TEST_F()
123 *ctx, sdbusplus::bus::match::rules::interfacesAdded( in TEST_F()
|
| /openbmc/phosphor-led-manager/manager/ |
| H A D | json-config.hpp | 41 sdbusplus::bus::match::rules::interfacesAdded() + in JsonConfig()
42 sdbusplus::bus::match::rules::sender( in JsonConfig()
|
| /openbmc/openbmc/meta-ibm/dynamic-layers/meta-openpower/recipes-phosphor/vpd/ |
| H A D | openpower-fru-vpd_%.bbappend | 23 rm ${D}/${nonarch_base_libdir}/udev/rules.d/70-op-vpd.rules
|
| /openbmc/sdbusplus/ |
| H A D | .flake8 | 1 # Autoformatter friendly flake8 config (all formatting rules disabled)
|
| /openbmc/linux/Documentation/userspace-api/ |
| H A D | landlock.rst | 28 Landlock rules
33 rights`_. A set of rules is aggregated in a ruleset, which can then restrict
39 We first need to define the ruleset that will contain our rules. For this
40 example, the ruleset will contain rules that only allow read actions, but write
97 This enables to create an inclusive ruleset that will contain our rules.
141 It may also be required to create rules following the same logic as explained
210 One policy layer grants access to a file path if at least one of its rules
226 be tied, either via the source or the destination path. These rules restrict
249 Landlock rules to itself, but they will not be automatically applied to other
265 process, a sandboxed process should have a subset of the target process rules,
[all …]
|
| /openbmc/linux/security/integrity/ima/ |
| H A D | Kconfig | 60 Disabling this option will disregard LSM based policy rules.
128 IMA policy can now be updated multiple times. The new rules get
129 appended to the original policy. Have in mind that the rules are
141 This option allows the root user to see the current policy rules.
167 bool "IMA build time configured policy rules"
174 policy rules persist after loading a custom policy.
176 Depending on the rules configured, this policy may require kernel
|
| /openbmc/linux/arch/x86/um/os-Linux/ |
| H A D | Makefile | 13 include $(srctree)/arch/um/scripts/Makefile.rules
|
| /openbmc/linux/fs/hostfs/ |
| H A D | Makefile | 13 include $(srctree)/arch/um/scripts/Makefile.rules
|
| /openbmc/linux/tools/power/acpi/tools/acpidbg/ |
| H A D | Makefile | 22 include ../../Makefile.rules
|
| /openbmc/linux/arch/um/kernel/skas/ |
| H A D | Makefile | 17 include $(srctree)/arch/um/scripts/Makefile.rules
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | BlueOak-1.0.0 | 14 rules. The rules of this license are both obligations
|
| /openbmc/linux/Documentation/admin-guide/aoe/ |
| H A D | udev-install.sh | 27 rules_d=/etc/udev/rules.d
|
| /openbmc/linux/arch/um/os-Linux/drivers/ |
| H A D | Makefile | 13 include $(srctree)/arch/um/scripts/Makefile.rules
|
| /openbmc/linux/drivers/net/dsa/sja1105/ |
| H A D | sja1105_flower.c | 12 list_for_each_entry(rule, &priv->flow_block.rules, list) in sja1105_rule_find()
94 list_add(&rule->list, &priv->flow_block.rules); in sja1105_setup_bcast_policer()
166 list_add(&rule->list, &priv->flow_block.rules); in sja1105_setup_tc_policer()
525 INIT_LIST_HEAD(&priv->flow_block.rules); in sja1105_flower_setup()
537 list_for_each_safe(pos, n, &priv->flow_block.rules) { in sja1105_flower_teardown()
|
| H A D | sja1105_vl.c | 102 list_for_each_entry(rule, &priv->flow_block.rules, list) { in sja1105_compose_gating_subschedule()
124 list_for_each_entry(rule, &priv->flow_block.rules, list) { in sja1105_compose_gating_subschedule()
326 list_for_each_entry(rule, &priv->flow_block.rules, list) { in sja1105_init_virtual_links()
396 list_for_each_entry(rule, &priv->flow_block.rules, list) { in sja1105_init_virtual_links()
534 list_add(&rule->list, &priv->flow_block.rules); in sja1105_vl_redirect()
629 list_add(&rule->list, &priv->flow_block.rules); in sja1105_vl_gate()
|
| /openbmc/linux/Documentation/networking/device_drivers/ethernet/aquantia/ |
| H A D | atlantic.rst | 256 RX flow rules (ntuple filters)
259 There are separate rules supported, that applies in that order:
261 1. 16 VLAN ID rules
262 2. 16 L2 EtherType rules
263 3. 8 L3/L4 5-Tuple rules
269 To enable or disable the RX flow rules::
277 Because of the fixed order of the rules, the location of filters is also fixed:
299 For ``flow-type ip4|udp4|tcp4|sctp4|ip6|udp6|tcp6|sctp6`` you can set 8 rules
300 for traffic IPv4 or you can set 2 rules for traffic IPv6. Loc number traffic
|
| /openbmc/phosphor-user-manager/phosphor-ldap-config/ |
| H A D | ldap_config.cpp | 65 bus, sdbusplus::bus::match::rules::interfacesAdded(certRootPath), in Config()
70 bus, sdbusplus::bus::match::rules::interfacesAdded(authObjPath), in Config()
76 sdbusplus::bus::match::rules::propertiesChanged(certObjPath, certIface), in Config()
116 bus, sdbusplus::bus::match::rules::interfacesAdded(certRootPath), in Config()
120 bus, sdbusplus::bus::match::rules::interfacesAdded(authObjPath), in Config()
125 sdbusplus::bus::match::rules::propertiesChanged(certObjPath, certIface), in Config()
|
| /openbmc/phosphor-objmgr/src/ |
| H A D | main.cpp | 446 sdbusplus::bus::match::rules::nameOwnerChanged(), in main()
468 sdbusplus::bus::match::rules::interfacesAdded(), in main()
537 sdbusplus::bus::match::rules::interfacesRemoved(), in main()
564 sdbusplus::bus::match::rules::interface( in main()
566 sdbusplus::bus::match::rules::member("PropertiesChanged") + in main()
567 sdbusplus::bus::match::rules::argN(0, assocDefsInterface), in main()
|
| /openbmc/openbmc/poky/meta/recipes-core/initrdscripts/files/ |
| H A D | init-install-efi-testfs.sh | 61 rm -f /etc/udev/rules.d/automount.rules
|
| /openbmc/linux/Documentation/networking/ |
| H A D | vrf.rst | 10 The VRF device combined with ip rules provides the ability to create virtual
21 the use of higher priority ip rules (Policy Based Routing, PBR) to take
22 precedence over the VRF device rules directing specific traffic as desired.
48 flow through the VRF device. Similarly on egress routing rules are used to
51 and out of the VRF as a whole\ [1]_. Similarly, netfilter\ [2]_ and tc rules
52 can be applied using the VRF device to specify rules that apply to the VRF
60 ingress device and both INPUT and PREROUTING rules with skb->dev set to
61 the VRF device. For egress POSTROUTING and OUTPUT rules can be written
76 with a different priority or install per-VRF rules.
78 Prior to the v4.8 kernel iif and oif rules are needed for each VRF device::
[all …]
|
| /openbmc/linux/Documentation/translations/zh_CN/process/ |
| H A D | license-rules.rst | 5 :Original: :ref:`Documentation/process/license-rules.rst <kernel_licensing>`
187 guidelines in the licensing rules documentation.
202 guidelines in the licensing rules documentation.
242 guidelines in the licensing rules documentation.
|
| /openbmc/linux/Documentation/powerpc/ |
| H A D | syscall64-abi.rst | 19 rules, with the following differences.
47 Register preservation rules
49 Register preservation rules match the ELF ABI calling sequence with some
136 Register preservation rules
|
| /openbmc/linux/Documentation/translations/zh_TW/process/ |
| H A D | license-rules.rst | 7 :Original: :ref:`Documentation/process/license-rules.rst <kernel_licensing>`
190 guidelines in the licensing rules documentation.
205 guidelines in the licensing rules documentation.
245 guidelines in the licensing rules documentation.
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | ima_policy | 11 by opening the file, writing the rules one at a time and
141 Example of measure rules using alternate PCRs::
171 Example of 'measure' and 'appraise' rules requiring fs-verity
188 All of these policy rules could, for example, be constrained
|