/openbmc/sdbusplus/test/utility/ |
H A D | type_traits.cpp | 39 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 D | redefined-type.err | 1 redefined-type.json: In enum 'Foo': 2 redefined-type.json:3: 'Foo' is already defined 3 redefined-type.json: In struct 'Foo':
|
H A D | redefined-type.json | 2 { 'struct': 'Foo', 'data': { 'one': 'str' } } 3 { 'enum': 'Foo', 'data': [ 'two' ] }
|
H A D | doc-bad-enum-member.json | 4 # @Foo: 8 { 'enum': 'Foo', 'data': [ 'b' ] }
|
H A D | struct-data-invalid.json | 1 { 'struct': 'Foo',
|
H A D | struct-member-invalid.json | 1 { 'struct': 'Foo',
|
H A D | features-deprecated-type.json | 2 { 'struct': 'Foo', 'data': {},
|
H A D | features-deprecated-type.err | 1 features-deprecated-type.json: In struct 'Foo':
|
H A D | reserved-member-q.err | 1 reserved-member-q.json: In struct 'Foo':
|
H A D | reserved-enum-q.err | 1 reserved-enum-q.json: In enum 'Foo':
|
H A D | struct-member-invalid-dict.err | 1 struct-member-invalid-dict.json: In struct 'Foo':
|
H A D | struct-data-invalid.err | 1 struct-data-invalid.json: In struct 'Foo':
|
H A D | struct-member-invalid-dict.json | 3 { 'struct': 'Foo',
|
H A D | struct-member-invalid.err | 1 struct-member-invalid.json: In struct 'Foo':
|
H A D | reserved-enum-q.json | 4 { 'enum': 'Foo', 'data': [ 'unix', 'q-Unix' ] }
|
H A D | reserved-member-q.json | 4 { 'struct': 'Foo', 'data': { 'unix':'int', 'q-unix':'bool' } }
|
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Common/Callout/ |
H A D | README.md | 34 `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 D | offset_of.rs | 111 struct Foo { struct 122 c: Foo, 131 c: Foo,
|
/openbmc/linux/Documentation/translations/zh_CN/rust/ |
H A D | coding-guidelines.rst | 67 /// Returns a new [`Foo`]. 76 pub fn f(x: i32) -> Foo {
|
/openbmc/openbmc/poky/meta/files/common-licenses/ |
H A D | PHP-3.0 | 26 conjunction with PHP by saying "Foo for PHP" instead of calling 27 it "PHP Foo" or "phpfoo"
|
H A D | PHP-3.01 | 13 …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 D | query_param_test.cpp | 554 "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 D | cpp-style-and-conventions.md | 212 class Foo 215 Foo(); 335 class Foo 340 template <typename T> using foo_t = Foo<T>::type;
|
/openbmc/docs/designs/ |
H A D | event-logging.md | 292 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 D | coding-guidelines.rst | 75 /// Returns a new [`Foo`]. 84 pub fn f(x: i32) -> Foo {
|