Searched refs:slashes (Results 1 – 16 of 16) sorted by relevance
| /openbmc/linux/scripts/dtc/ |
| H A D | srcpos.c | 61 int slashes = 0; in shorten_to_initial_path() local
68 slashes++; in shorten_to_initial_path()
73 int diff = initial_pathlen - slashes, i, j; in shorten_to_initial_path()
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | binfmt-misc.rst | 26 name below ``/proc/sys/fs/binfmt_misc``; cannot contain slashes ``/`` for
42 Extension matching is case sensitive, and slashes ``/`` are not allowed!
|
| /openbmc/openbmc/poky/scripts/ |
| H A D | combo-layer.conf.example | 52 # Wildcards are applied to the complete path and also match slashes.
|
| /openbmc/linux/Documentation/driver-api/media/drivers/ |
| H A D | sh_mobile_ceu_camera.rst | 45 In the above chart minuses and slashes represent "real" data amounts, points and
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/libtar/files/ |
| H A D | CVE-2013-4420.patch | 19 by skipping over leading slashes and any prefix containing ".." components.
|
| /openbmc/openbmc/poky/meta/recipes-extended/gperf/gperf/ |
| H A D | 1862c6e57a308a05889c80c048dbc58bdc378dcb.patch | 108 + alternating components and slashes.
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-class-rnbd-client | 130 - If the 'device_path' provided during mapping contains slashes ("/"),
|
| /openbmc/docs/designs/ |
| H A D | binarystore-via-blobs.md | 65 ASCII alphanumerical characters and forward slashes ('/').
|
| /openbmc/boost-dbus/cmake/ |
| H A D | HunterGate.cmake | 461 # Beautify path, fix probable problems with windows path slashes
|
| /openbmc/linux/Documentation/trace/coresight/ |
| H A D | coresight.rst | 471 listed along with configuration options within forward slashes '/'. Since a
492 The syntax within the forward slashes '/' is important. The '@' character
|
| /openbmc/linux/Documentation/filesystems/ |
| H A D | path-lookup.rst | 41 of elements: "slashes" that are sequences of one or more "``/``"
44 start with slashes are "absolute" and start from the filesystem root.
53 slashes and components, it can be empty, in other words. This is
68 pathname that is just slashes have a final component. If it does
510 won't try to create that name. They also check for trailing slashes
|
| /openbmc/openbmc/poky/documentation/migration-guides/ |
| H A D | migration-3.2.rst | 193 - A trailing slash or duplicated slashes in the value of :term:`S` or :term:`B`
|
| /openbmc/linux/fs/ |
| H A D | namei.c | 103 * if the pathname has trailing slashes - follow.
2310 * slash, and continue until no more slashes. in link_path_walk()
3539 /* trailing slashes? */ in open_last_lookups()
4383 goto slashes; in do_unlinkat()
4386 goto slashes; in do_unlinkat()
4417 slashes: in do_unlinkat()
4994 /* unless the source is a directory trailing slashes give -ENOTDIR */ in do_renameat2()
|
| /openbmc/linux/tools/perf/Documentation/ |
| H A D | perf-intel-pt.txt | 225 selected by providing the PMU name followed by the "config" separated by slashes.
|
| /openbmc/linux/Documentation/sound/kernel-api/ |
| H A D | writing-an-alsa-driver.rst | 1073 device. Note that you must not use slashes (“/”) in this string.
|
| /openbmc/openbmc/poky/meta/recipes-devtools/binutils/binutils/ |
| H A D | 0008-Use-libtool-2.4.patch | 25429 +# which contains forward slashes, into one that contains
|