Home
last modified time | relevance | path

Searched refs:Foo (Results 1 – 25 of 38) sorted by relevance

12

/openbmc/sdbusplus/test/utility/
H A Dtype_traits.cpp39 struct Foo in TEST() struct
49 ASSERT_THAT(has_member_find_v<Foo>, Eq(true)); in TEST()
50 ASSERT_THAT(has_member_find_v<Foo&>, Eq(true)); in TEST()
51 ASSERT_THAT(has_member_find_v<const Foo&>, Eq(true)); in TEST()
67 struct Foo in TEST() struct
77 ASSERT_THAT(has_member_contains_v<Foo>, Eq(true)); in TEST()
78 ASSERT_THAT(has_member_contains_v<Foo&>, Eq(true)); in TEST()
79 ASSERT_THAT(has_member_contains_v<const Foo&>, Eq(true)); in TEST()
/openbmc/qemu/tests/qapi-schema/
H A Dredefined-type.err1 redefined-type.json: In enum 'Foo':
2 redefined-type.json:3: 'Foo' is already defined
3 redefined-type.json: In struct 'Foo':
H A Dredefined-type.json2 { 'struct': 'Foo', 'data': { 'one': 'str' } }
3 { 'enum': 'Foo', 'data': [ 'two' ] }
H A Ddoc-bad-enum-member.json4 # @Foo:
8 { 'enum': 'Foo', 'data': [ 'b' ] }
H A Dstruct-data-invalid.json1 { 'struct': 'Foo',
H A Dstruct-member-invalid.json1 { 'struct': 'Foo',
H A Dfeatures-deprecated-type.json2 { 'struct': 'Foo', 'data': {},
H A Dfeatures-deprecated-type.err1 features-deprecated-type.json: In struct 'Foo':
H A Dreserved-member-q.err1 reserved-member-q.json: In struct 'Foo':
H A Dreserved-enum-q.err1 reserved-enum-q.json: In enum 'Foo':
H A Dstruct-member-invalid-dict.err1 struct-member-invalid-dict.json: In struct 'Foo':
H A Dstruct-data-invalid.err1 struct-data-invalid.json: In struct 'Foo':
H A Dstruct-member-invalid-dict.json3 { 'struct': 'Foo',
H A Dstruct-member-invalid.err1 struct-member-invalid.json: In struct 'Foo':
H A Dreserved-enum-q.json4 { 'enum': 'Foo', 'data': [ 'unix', 'q-Unix' ] }
H A Dreserved-member-q.json4 { 'struct': 'Foo', 'data': { 'unix':'int', 'q-unix':'bool' } }
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Common/Callout/
H A DREADME.md34 `xyz.openbmc_project.Error.Foo` may want to add an IIC callout. This is
35 indicated in Foo's YAML interface as follows :
38 - name: Foo
39 description: this is the error Foo
44 The way this inheritance will be implemented is that, Foo's metadata will
46 will have to provide values for Foo and IIC metadata. Like mentioned before, due
48 figure out that the error Foo includes an IIC callout.
/openbmc/qemu/rust/qemu-api/src/
H A Doffset_of.rs111 struct Foo { struct
122 c: Foo,
131 c: Foo,
/openbmc/linux/Documentation/translations/zh_CN/rust/
H A Dcoding-guidelines.rst67 /// Returns a new [`Foo`].
76 pub fn f(x: i32) -> Foo {
/openbmc/openbmc/poky/meta/files/common-licenses/
H A DPHP-3.026 conjunction with PHP by saying "Foo for PHP" instead of calling
27 it "PHP Foo" or "phpfoo"
H A DPHP-3.0113 …your software works in conjunction with PHP by saying "Foo for PHP" instead of calling it "PHP Foo
/openbmc/bmcweb/test/redfish-core/include/utils/
H A Dquery_param_test.cpp554 "Foo" : {"@odata.id": "/foobar"}})"_json; in TEST()
582 "Foo" : {"@odata.id": "/foobar"}})"_json; in TEST()
692 "Foo": { in TEST()
697 "Foo": { in TEST()
/openbmc/docs/
H A Dcpp-style-and-conventions.md212 class Foo
215 Foo();
335 class Foo
340 template <typename T> using foo_t = Foo<T>::type;
/openbmc/docs/designs/
H A Devent-logging.md292 The `Foo.errors.yaml` content will be combined with the content formerly in the
293 `Foo.metadata.yaml` files specified by `phosphor-logging` and specified by a new
294 file type `Foo.events.yaml`. This `Foo.events.yaml` format will cover both the
297 Message Registries. The current `Foo.errors.yaml` and `Foo.metadata.yaml` files
333 Refactoring will be done to migrate existing `Foo.metadata.yaml` and
334 `Foo.errors.yaml` content to the `Foo.events.yaml` as migration is done by
/openbmc/linux/Documentation/rust/
H A Dcoding-guidelines.rst75 /// Returns a new [`Foo`].
84 pub fn f(x: i32) -> Foo {

12