| /Linux-v5.4/lib/ |
| D | test_objagg.c | 29 struct world { struct
46 static struct objagg_obj *world_obj_get(struct world *world, in world_obj_get() argument
60 if (!world->key_refs[key_id_index(key_id)]) { in world_obj_get()
61 world->objagg_objs[key_id_index(key_id)] = objagg_obj; in world_obj_get()
62 } else if (world->objagg_objs[key_id_index(key_id)] != objagg_obj) { in world_obj_get()
68 world->key_refs[key_id_index(key_id)]++; in world_obj_get()
76 static void world_obj_put(struct world *world, struct objagg *objagg, in world_obj_put() argument
81 if (!world->key_refs[key_id_index(key_id)]) in world_obj_put()
83 objagg_obj = world->objagg_objs[key_id_index(key_id)]; in world_obj_put()
85 world->key_refs[key_id_index(key_id)]--; in world_obj_put()
[all …]
|
| /Linux-v5.4/Documentation/devicetree/bindings/arm/ |
| D | secure.txt | 1 * ARM Secure world bindings
6 world or the Secure world. However some devicetree consumers are
13 The general principle of the naming scheme for Secure world bindings
14 is that any property that needs a different value in the Secure world
19 world value is the same as specified for the Normal world by the
30 world consumers (like kernels that run entirely in Secure) to simply
31 describe the view of Secure world using the standard bindings. These
33 world views need to be described in a single device tree.
35 Valid Secure world properties
39 in the secure world. The combination of this with "status" allows
[all …]
|
| /Linux-v5.4/scripts/kconfig/tests/preprocess/builtin_func/ |
| D | expected_stderr | 1 Kconfig:8: hello world 1
2 Kconfig:18: hello world 3
3 Kconfig:22: hello world 4
|
| D | Kconfig | 4 $(info,hello world 0)
8 $(warning-if,y,hello world 1)
18 $(warning,$(shell,echo hello world 3))
|
| D | expected_stdout | 1 hello world 0
|
| /Linux-v5.4/Documentation/devicetree/bindings/iio/ |
| D | mount-matrix.txt | 13 that produce three-dimensional data in relation to the world where it is
41 external world, the environment where the device is deployed. Usually the data
43 to this world. When using the mounting matrix, the sensor and device orientation
45 world.
47 Device-to-world examples for some three-dimensional sensor types:
49 - Accelerometers have their world frame of reference toward the center of
53 this point. Up and down in the world relative to the device frame of
93 - Magnetometers (compasses) have their world frame of reference relative to the
94 geomagnetic field. The system orientation vis-a-vis the world is defined with
160 space, relative to the device or world point of reference.
|
| /Linux-v5.4/scripts/kconfig/tests/preprocess/escape/ |
| D | expected_stderr | 1 Kconfig:9: hello, world
|
| D | Kconfig | 9 $(warning,hello$(comma) world)
|
| /Linux-v5.4/Documentation/kbuild/ |
| D | kconfig-macro-language.rst | 181 For example, $(shell echo hello, world) runs the command "echo hello, world".
182 Likewise, $(info hello, world) prints "hello, world" to stdout. You could say
188 $(shell, echo hello, world)
194 $(shell, echo hello$(comma) world)
|
| /Linux-v5.4/drivers/of/unittest-data/ |
| D | testcases.dts | 9 prop-remove = "world";
|
| /Linux-v5.4/drivers/parport/ |
| D | TODO-parport | 14 with (maybe just log) whatever the printer wants to tell the world.
|
| /Linux-v5.4/fs/9p/ |
| D | Kconfig | 27 groups beyond the owner/group/world scheme.
|
| /Linux-v5.4/fs/ext2/ |
| D | Kconfig | 27 groups beyond the owner/group/world scheme.
|
| /Linux-v5.4/Documentation/ |
| D | tee.txt | 88 User space Kernel Secure world
108 RPC (Remote Procedure Call) are requests from secure world to kernel driver
|
| /Linux-v5.4/fs/ceph/ |
| D | Kconfig | 36 groups beyond the owner/group/world scheme.
|
| /Linux-v5.4/Documentation/devicetree/bindings/dma/ |
| D | qcom_bam_dma.txt | 15 the secure world.
|
| D | qcom_adm.txt | 18 - qcom,ee: indicates the security domain identifier used in the secure world.
|
| /Linux-v5.4/fs/jfs/ |
| D | Kconfig | 18 groups beyond the owner/group/world scheme.
|
| /Linux-v5.4/Documentation/driver-api/memory-devices/ |
| D | ti-emif.rst | 48 Interface to the external world
|
| /Linux-v5.4/Documentation/admin-guide/sysctl/ |
| D | fs.rst | 211 in world writable sticky directories, unless they are owned by the
223 time-of-check-time-of-use race, most commonly seen in world-writable
249 don't own in world writable sticky directories, unless they are
259 time-of-check-time-of-use race, most commonly seen in world-writable
269 a sticky world-writable directory, or when the uid of the symlink and
|
| /Linux-v5.4/arch/um/drivers/ |
| D | Kconfig | 138 machines on the outside world.
171 outside world, say Y to this, the Daemon Transport and/or the
208 outside world), and/or the Daemon transport (to network multiple
253 with the rest of the world using Virtual Distributed Ethernet,
321 to the outside world that the host user is permitted, and unlike
|
| /Linux-v5.4/Documentation/devicetree/bindings/firmware/ |
| D | intel,stratix10-svc.txt | 10 communication with SDM, only the secure world of software (EL3, Exception
|
| /Linux-v5.4/Documentation/networking/ |
| D | ray_cs.txt | 3 Copyright (c) 1998 Corey Thomas (corey@world.std.com)
17 and I can be emailed at corey@world.std.com
|
| /Linux-v5.4/fs/isofs/ |
| D | Kconfig | 26 characters of almost all languages of the world; see
|
| /Linux-v5.4/Documentation/arm/ |
| D | firmware.rst | 8 world, which changes the way some things have to be initialized. This makes
|
