| /openbmc/phosphor-power/phosphor-power-supply/test/ |
| H A D | power_supply_tests.cpp | 41 const PMBusExpectations& expectations) in setPMBusExpectations() argument
45 .WillOnce(Return(expectations.statusWordValue)); in setPMBusExpectations()
47 if (expectations.statusWordValue != 0) in setPMBusExpectations()
54 .WillOnce(Return(expectations.statusInputValue)); in setPMBusExpectations()
57 .WillOnce(Return(expectations.statusMFRValue)); in setPMBusExpectations()
60 .WillOnce(Return(expectations.statusCMLValue)); in setPMBusExpectations()
67 .WillOnce(Return(expectations.statusVOUTValue)); in setPMBusExpectations()
70 .WillOnce(Return(expectations.statusIOUTValue)); in setPMBusExpectations()
73 .WillOnce(Return(expectations.statusFans12Value)); in setPMBusExpectations()
76 .WillOnce(Return(expectations.statusTempValue)); in setPMBusExpectations()
[all …]
|
| /openbmc/phosphor-dbus-interfaces/ |
| H A D | README.md | 7 through the documented set of the common [requirements and expectations][].
33 [requirements and expectations]: requirements.md
|
| H A D | requirements.md | 3 This document outlines requirements and expectations for dbus interfaces. These
|
| /openbmc/docs/ |
| H A D | community-membership.md | 3 This doc outlines the various expectations of contributor roles in OpenBMC. The
27 Role-specific expectations, responsibilities, and requirements are enumerated
90 - Expected to be responsive to review requests as per [community expectations]
129 - Expected to be responsive to review requests as per [community expectations]
160 - **Note the following expectations for sponsors**:
179 - Expected to be responsive to review requests as per [community expectations]
258 changes and expectations (emails, GitHub issues, meetings)
282 [community expectations]: /code-of-conduct.md
|
| /openbmc/linux/Documentation/maintainer/ |
| H A D | feature-and-driver-maintainers.rst | 12 populous) group. It provides tips and describes the expectations and
31 The exact expectations on the response time will vary by subsystem.
35 review delay of the subsystem maintainer. The resulting expectations
89 The previous section described the expectations of the maintainer,
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Configuration/ |
| H A D | README.md | 4 expectations we typically use elsewhere in this repository. Any types and
|
| /openbmc/phosphor-fan-presence/docs/presence/ |
| H A D | rpolicy.md | 7 use those methods can be configured based on system expectations.
|
| /openbmc/linux/Documentation/dev-tools/kunit/ |
| H A D | usage.rst | 11 and then sets *expectations* for what should happen. For example:
25 nothing; no expectations are set, and therefore all expectations pass. On the
34 expectations about the behavior of a piece of code under test. When one or more
35 expectations fail, the test case fails and information about the failure is
51 expectations, the test case, ``add_test_basic`` will pass; if any one of these
52 expectations fails, the test case will fail.
55 continue to run, and try other expectations until the test case ends or is
59 To learn about more KUnit expectations, see Documentation/dev-tools/kunit/api/test.rst.
|
| H A D | architecture.rst | 108 KUnit tests verify state using expectations/assertions.
109 All expectations/assertions are formatted as:
116 - For expectations, the test is marked as failed and the failure is logged.
|
| /openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/ |
| H A D | python3-pylint_3.3.3.bb | 8 file://0001-Adjust-test-expectations-for-ptest.patch \
|
| /openbmc/linux/drivers/soc/rockchip/ |
| H A D | Kconfig | 15 to make some of them conform to expectations of the kernel.
|
| /openbmc/linux/Documentation/process/ |
| H A D | code-of-conduct-interpretation.rst | 68 secondary by the expectations of contributors and maintainers.
70 Both the expertise expectations and decision-making are subject to
76 As a consequence, setting expertise expectations, making decisions and
|
| H A D | contribution-maturity-model.rst | 24 expectations for upstream community engagement aim to increase the
|
| /openbmc/linux/net/netfilter/ |
| H A D | nf_conntrack_expect.c | 239 hlist_for_each_entry_safe(exp, next, &help->expectations, lnode) { in nf_ct_remove_expectations()
405 hlist_add_head_rcu(&exp->lnode, &master_help->expectations); in nf_ct_expect_insert()
422 hlist_for_each_entry(exp, &master_help->expectations, lnode) { in evict_oldest_expect()
|
| /openbmc/linux/include/net/netfilter/ |
| H A D | nf_conntrack_helper.h | 74 struct hlist_head expectations; member
|
| /openbmc/openbmc/poky/meta/recipes-devtools/dpkg/dpkg/ |
| H A D | 0001-script.c-avoid-use-of-chroot.patch | 7 don't expect a chroot. This matches up our system expectations with what
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | index.rst | 63 subsystems expectations will be found here.
|
| /openbmc/linux/Documentation/ |
| H A D | index.rst | 86 The following holds information on the kernel's expectations regarding the
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/luajit/ |
| H A D | luajit_git.bb | 65 # expectations.
|
| /openbmc/linux/Documentation/filesystems/ |
| H A D | dnotify.rst | 43 Implementation expectations (features and bugs :-))
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-core/toybox/ |
| H A D | toybox_0.8.12.bb | 20 # Fix CC, CFLAGS, CROSS_COMPILE to match expectations.
|
| /openbmc/openbmc/poky/bitbake/lib/bb/fetch2/ |
| H A D | README | 1 There are expectations of users of the fetcher code. This file attempts to document
|
| /openbmc/linux/Documentation/driver-api/driver-model/ |
| H A D | device.rst | 111 strict expectations on when attributes get created. When a new device is
|
| /openbmc/linux/drivers/fsi/ |
| H A D | Kconfig | 26 to match old userspace expectations.
|
| /openbmc/docs/security/ |
| H A D | obmc-security-response-team-guidelines.md | 11 Here are the primary expectations:
118 - Set expectations for follow-up communications.
|