Searched refs:rules (Results 901 – 925 of 963) sorted by relevance
1...<<313233343536373839
/openbmc/x86-power-control/src/ |
H A D | power_control.cpp | 903 namespace match_rules = sdbusplus::bus::match::rules;
|
/openbmc/linux/Documentation/filesystems/ |
H A D | xfs-delayed-logging-design.rst | 50 performed. The logging subsystem only cares that certain specific rules are 275 rules.
|
H A D | overlayfs.rst | 622 following rules apply:
|
H A D | xfs-online-fsck-design.rst | 248 sharing and lock acquisition rules as the regular filesystem. 376 Scrub obeys the same rules as regular filesystem accesses for resource and lock 1559 Deadlock avoidance rules require that AGs only be locked in increasing order, 1665 However, online fsck changes the rules -- remember that although physical 3565 These rules must be followed to ensure correct interactions between the 3585 - The hook function can abort the inode scan to avoid breaking the other rules.
|
H A D | path-lookup.rst | 23 many rules, special cases, and implementation alternatives that all 607 direction: unfamiliarity. The locking rules when depending on RCU are
|
/openbmc/openbmc/meta-openembedded/meta-oe/licenses/ |
H A D | SSPL-1 | 265 rules and protocols for communication across the network.
|
/openbmc/openbmc/poky/meta/files/common-licenses/ |
H A D | RPL-1.5 | 505 under the rules then prevailing of the American Arbitration Association. You
|
H A D | SSPL-1.0 | 265 rules and protocols for communication across the network.
|
H A D | GPL-3.0-only | 105 …rially and adversely affects the operation of the network or violates the rules and protocols for …
|
H A D | AGPL-3.0-or-later | 295 of the network or violates the rules and protocols for communication across
|
H A D | AGPL-3.0-only | 322 adversely affects the operation of the network or violates the rules and
|
H A D | GPL-3.0-or-later | 306 of the network or violates the rules and protocols for communication across
|
H A D | RPL-1.1 | 165 …ating to this License shall be submitted to binding arbitration under the rules then prevailing of…
|
/openbmc/u-boot/tools/binman/ |
H A D | README | 60 It is of course possible to add more and more build rules to the U-Boot
|
/openbmc/qemu/docs/interop/ |
H A D | qcow2.txt | 193 formally, additional fields have the following compatibility rules:
|
/openbmc/linux/Documentation/bpf/ |
H A D | bpf_devel_QA.rst | 417 A: The same rules apply as with netdev patch submissions in general, see
|
/openbmc/linux/Documentation/core-api/ |
H A D | dma-api-howto.rst | 116 set of rules regarding this, and this text is an attempt to finally
|
/openbmc/u-boot/ |
H A D | README | 222 SPL and U-Boot proper (i.e. they both follow the same rules). 3895 General rules: 4904 Please also stick to the following formatting rules: 4919 establish some rules. Submissions which do not conform to these rules
|
/openbmc/linux/Documentation/admin-guide/ |
H A D | reporting-issues.rst | 305 explain how to do that once it rules out other potential causes for your issue. 1583 within rules outlined in Documentation/process/stable-kernel-rules.rst.
|
/openbmc/linux/Documentation/driver-api/usb/ |
H A D | power-management.rst | 619 runtime rules and require the attached child device and all descendants to be
|
/openbmc/ipmi-fru-parser/ |
H A D | LICENSE | 334 adversely affects the operation of the network or violates the rules and
|
/openbmc/linux/drivers/net/dsa/sja1105/ |
H A D | sja1105_main.c | 2441 list_for_each_entry(rule, &priv->flow_block.rules, list) { in sja1105_vlan_filtering()
|
/openbmc/linux/Documentation/dev-tools/ |
H A D | checkpatch.rst | 1253 See: https://www.kernel.org/doc/html/latest/process/license-rules.html
|
/openbmc/linux/Documentation/admin-guide/pm/ |
H A D | intel_pstate.rst | 515 on the following rules, regardless of the current operation mode of the driver:
|
/openbmc/linux/drivers/net/ethernet/broadcom/bnx2x/ |
H A D | bnx2x_ethtool.c | 3364 u32 *rules __always_unused) in bnx2x_get_rxnfc()
|
1...<<313233343536373839