| /openbmc/openbmc/poky/bitbake/lib/bb/ |
| H A D | xattr.py | 20 def listxattr(path, follow=True): argument
21 func = libc.listxattr if follow else libc.llistxattr
59 def getxattr(path, name, follow=True): argument
60 func = libc.getxattr if follow else libc.lgetxattr
87 def get_all_xattr(path, follow=True): argument
90 names = listxattr(path, follow)
93 value = getxattr(path, name, follow)
|
| /openbmc/linux/Documentation/devicetree/bindings/regulator/ |
| H A D | qcom,spmi-regulator.yaml | 60 BIT(0) = follow HW0_EN signal
61 BIT(1) = follow HW1_EN signal
62 BIT(2) = follow HW2_EN signal
63 BIT(3) = follow HW3_EN signal
74 BIT(0) = follow HW0_EN signal
75 BIT(1) = follow HW1_EN signal
76 BIT(2) = follow HW2_EN signal
77 BIT(3) = follow HW3_EN signal
78 BIT(4) = follow PMIC awake state
|
| /openbmc/openbmc-test-automation/docs/ |
| H A D | gui_setup_reference.md | 35 - Python Installation: Please follow the documented procedure available.
37 - Firefox Installation: Please follow the documented procedure available.
39 - geckodriver installation: Please follow the documented procedure available.
|
| /openbmc/openbmc/poky/meta/recipes-graphics/xorg-app/ |
| H A D | xeyes_1.3.0.bb | 3 SUMMARY = "X11 eyes that follow the mouse cursor demo"
5 follow the location of the mouse cursor around the screen."
|
| /openbmc/openbmc/poky/meta/recipes-extended/unzip/unzip/ |
| H A D | 06-unzip60-alt-iconv-utf8_CVE-2015-1315.patch | 178 -x exclude filenames that follow from listing\n";
184 + -x exclude filenames that follow from listing\n\
247 + "error: a valid character encoding should follow the -I argument"));
255 + "error: a valid character encoding should follow the -I argument"));
283 + "error: a valid character encoding should follow the -I argument"));
291 + "error: a valid character encoding should follow the -O argument"));
347 + "error: a valid character encoding should follow the -I argument"));
355 + "error: a valid character encoding should follow the -I argument"));
383 + "error: a valid character encoding should follow the -I argument"));
391 + "error: a valid character encoding should follow the -O argument"));
|
| /openbmc/linux/Documentation/devicetree/bindings/mfd/ |
| H A D | canaan,k210-sysctl.yaml | 42 should follow the bindings specified in
51 should follow the bindings specified in
60 should follow the bindings specified in
|
| H A D | brcm,bcm6358-gpio-sysctl.yaml | 41 should follow the bindings specified in
50 should follow the bindings specified in
|
| H A D | brcm,bcm6328-gpio-sysctl.yaml | 41 should follow the bindings specified in
50 should follow the bindings specified in
|
| H A D | brcm,bcm6318-gpio-sysctl.yaml | 41 should follow the bindings specified in
50 should follow the bindings specified in
|
| H A D | brcm,bcm63268-gpio-sysctl.yaml | 41 should follow the bindings specified in
50 should follow the bindings specified in
|
| /openbmc/linux/fs/btrfs/ |
| H A D | print-tree.h | 13 void btrfs_print_tree(const struct extent_buffer *c, bool follow);
|
| H A D | print-tree.c | 356 void btrfs_print_tree(const struct extent_buffer *c, bool follow) in btrfs_print_tree() argument
385 if (!follow) in btrfs_print_tree()
411 btrfs_print_tree(next, follow); in btrfs_print_tree()
|
| /openbmc/openbmc/poky/meta/recipes-devtools/patch/patch/ |
| H A D | CVE-2019-13636.patch | 4 Subject: Don't follow symlinks unless --follow-symlinks is given
7 append_to_file): Unless the --follow-symlinks option is given, open files with
|
| /openbmc/sdeventplus/example/ |
| H A D | meson.build | 3 'follow',
|
| /openbmc/docs/designs/ |
| H A D | README.md | 3 Newly authored design documents are encouraged to follow the
|
| /openbmc/bios-bmc-smm-error-logger/ |
| H A D | README.md | 3 This daemon will follow the design doc:
|
| /openbmc/openbmc-test-automation/ffdc/docs/ |
| H A D | yaml_syntax_rules.md | 16 follow while writing a YAML block. The YAML standards applies as usual.
29 This block statement in YAML one must follow for the collector to do operation
|
| /openbmc/telemetry/ |
| H A D | README.md | 29 To build it using bitbake follow the guide from OpenBMC docs`[5]`. To build it
30 using meson follow the quick guide to install meson`[6]` and then run below
|
| /openbmc/qemu/ |
| H A D | .gdbinit | 2 # follow the instructions it prints. They boil down to adding the following to
|
| /openbmc/linux/scripts/ |
| H A D | dev-needs.sh | 40 --exclude-devlinks Don't follow device links when tracking probe
125 # They can also have cycles. So, don't follow them.
|
| /openbmc/linux/tools/testing/selftests/lkdtm/ |
| H A D | stack-entropy.sh | 24 dmesg --follow >"$log" & pid=$!
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/libgxim/libgxim/ |
| H A D | multi-line-ACLOCAL_AMFLAGS-isnot-supported-by-autoreconf.patch | 4 It will cause configure error as follow.
|
| /openbmc/linux/fs/coda/ |
| H A D | pioctl.c | 69 data.follow ? LOOKUP_FOLLOW : 0, &path); in coda_pioctl()
|
| /openbmc/openbmc/meta-arm/ |
| H A D | README.md | 49 Commits and patches added should follow the OpenEmbedded patch guidelines:
61 We follow the Yocto Project release methodology, schedule, and stable/LTS support timelines. For m…
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | GPL-2.0-with-autoconf-exception | 4 … that are the output of Autoconf when processing the Macro. You need not follow the terms of the G…
|