Home
last modified time | relevance | path

Searched refs:renaming (Results 1 – 25 of 54) sorted by relevance

123

/openbmc/openbmc/poky/meta/recipes-support/libsoup/
H A Dlibsoup_3.4.4.bb51 # and will therefore become subject to renaming by debian.bbclass. Prevent
52 # renaming in order to keep the package name consistent regardless of whether
H A Dlibsoup-2.4_2.74.3.bb51 # and will therefore become subject to renaming by debian.bbclass. Prevent
52 # renaming in order to keep the package name consistent regardless of whether
/openbmc/openbmc/meta-google/recipes-google/networking/
H A Dgbmc-nic-rename.bb18 # install dev renaming files if any
/openbmc/linux/Documentation/arch/openrisc/
H A Dtodo.rst12 - Finish the renaming cleanup... there are references to or32 in the code
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-connectivity/openconnect/
H A Dopenconnect_9.12.bb7 file://0001-Shim-for-renaming-of-GNUTLS_NO_EXTENSIONS-in-GnuTLS-.patch \
/openbmc/openbmc/meta-openembedded/meta-perl/recipes-perl/libsub/
H A Dlibsub-exporter-progressive-perl_0.001013.bb7 features, like renaming exports, if they try to use them."
/openbmc/linux/tools/testing/selftests/prctl/
H A Dset-anon-vma-name-test.c92 TEST_F(vma, renaming) { in TEST_F() argument
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-connectivity/openconnect/openconnect/
H A D0001-Shim-for-renaming-of-GNUTLS_NO_EXTENSIONS-in-GnuTLS-.patch4 Subject: [PATCH] Shim for renaming of GNUTLS_NO_EXTENSIONS in GnuTLS v3.8.1
/openbmc/openbmc/poky/meta/classes-global/
H A Ddebian.bbclass7 # Debian package renaming only occurs when a package is built
123 bb.note("debian: renaming %s to %s" % (pkg, newpkg))
H A Dpackage_ipk.bbclass284 # Needed to ensure PKG_xxx renaming of dependency packages works
/openbmc/openbmc/meta-openembedded/meta-filesystems/recipes-support/fuse/
H A Dfuse3_3.16.2.bb77 # Forbid auto-renaming to libfuse3-utils
H A Dfuse_2.9.9.bb49 # Forbid auto-renaming to libfuse-utils
/openbmc/linux/Documentation/userspace-api/
H A Dlandlock.rst188 relevant when we want to allow linking or renaming. Indeed, having consistent
390 As for file renaming and linking, a sandboxed thread cannot modify its
428 File renaming and linking (ABI < 2)
439 escalations through renaming or linking, and for the sake of simplicity,
440 Landlock previously limited linking and renaming to the same directory.
442 control renaming and linking thanks to the new ``LANDLOCK_ACCESS_FS_REFER``
/openbmc/linux/Documentation/networking/device_drivers/ethernet/ti/
H A Dcpsw_switchdev.rst9 Port renaming
12 On older udev versions renaming of ethX to swXpY will not be automatically
H A Dam65_nuss_cpsw_switchdev.rst9 Port renaming
/openbmc/openbmc/meta-openembedded/meta-gnome/recipes-graphics/cogl/
H A Dcogl-1.0.inc77 # For backwards compatibility after Debian-renaming
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/multipath-tools/files/
H A D0003-RH-don-t-start-without-a-config-file.patch10 simple way to disable multipath. Simply removing or renaming
/openbmc/linux/fs/ntfs/
H A DKconfig62 renaming is possible. Note only non-resident files can be written to
/openbmc/openbmc/poky/meta/recipes-support/db/db/
H A D0001-Fix-libc-compatibility-by-renaming-atomic_init-API.patch4 Subject: [PATCH] Fix libc++ compatibility by renaming atomic_init API
/openbmc/openbmc/poky/meta/recipes-support/db/
H A Ddb_5.3.28.bb28 file://0001-Fix-libc-compatibility-by-renaming-atomic_init-API.patch \
/openbmc/linux/Documentation/filesystems/
H A Dntfs3.rst74 when creating and moving or renaming files. Files whose names start
/openbmc/linux/fs/overlayfs/
H A DKconfig19 redirects when renaming directories by default. In this case it is
/openbmc/docs/development/
H A Ddevtool-hello-world.md119 will save you time and grief. No more renaming and recovering original files,
/openbmc/openbmc/meta-raspberrypi/classes/
H A Dsdcard_image-rpi.bbclass142 # Split entry at optional ':' to enable file renaming for the destination
/openbmc/linux/Documentation/i2c/
H A Di2c-sysfs.rst107 instead of renaming or mapping them, so that it may be less confusing to other
158 follows the common practice by not renaming physical I2C buses, this should also

123