Home
last modified time | relevance | path

Searched refs:behaviour (Results 1 – 25 of 129) sorted by relevance

123456

/openbmc/openbmc/poky/meta/recipes-core/busybox/busybox/
H A Dfail_on_no_media.patch9 The current behaviour of busybox is to try all fstype when automounting
11 media exists, so change the behaviour of busybox to do the same.
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-core/sdbus-c++/sdbus-c++-libsystemd/
H A D0007-don-t-pass-AT_SYMLINK_NOFOLLOW-flag-to-faccessat.patch17 with (flag == 0) and (flag == AT_SYMLINK_NOFOLLOW) is the behaviour
23 just historical and not actually necessary or desired behaviour?
53 + behaviour for broken symlinks; laccess() on a broken symlink will succeed
58 + and not actually necessary or desired behaviour?
/openbmc/openbmc/meta-openembedded/meta-perl/recipes-perl/libstrictures/
H A Dlibstrictures-perl_2.000006.bb12 and then unknown (and probably undesired) subsequent behaviour. \
21 causes undesired behaviour this can be overridden by setting the \
/openbmc/openbmc/poky/meta/classes-recipe/
H A Dsetuptools3_legacy.bbclass7 # This class is for packages which use the deprecated setuptools behaviour,
9 # This behaviour is deprecated in setuptools[1] and won't work in the future, so
/openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/
H A Dpython3-prctl_1.8.1.bb3 process' behaviour. Usage of the function is fairly messy though, due to \
/openbmc/qemu/hw/ppc/
H A Dspapr_hcall.c1411 uint64_t behaviour = H_CPU_BEHAV_FAVOUR_SECURITY; in h_get_cpu_characteristics() local
1423 behaviour |= H_CPU_BEHAV_L1D_FLUSH_PR; in h_get_cpu_characteristics()
1426 behaviour |= H_CPU_BEHAV_NO_L1D_FLUSH_ENTRY; in h_get_cpu_characteristics()
1427 behaviour |= H_CPU_BEHAV_NO_L1D_FLUSH_UACCESS; in h_get_cpu_characteristics()
1431 behaviour |= H_CPU_BEHAV_L1D_FLUSH_PR; in h_get_cpu_characteristics()
1438 behaviour |= H_CPU_BEHAV_BNDS_CHK_SPEC_BAR; in h_get_cpu_characteristics()
1444 behaviour |= H_CPU_BEHAV_BNDS_CHK_SPEC_BAR; in h_get_cpu_characteristics()
1458 behaviour |= H_CPU_BEHAV_FLUSH_COUNT_CACHE; in h_get_cpu_characteristics()
1469 args[1] = behaviour; in h_get_cpu_characteristics()
/openbmc/openbmc/meta-openembedded/meta-gnome/recipes-gimp/mypaint/libmypaint/
H A D0001-make-build-compatible-w.-autoconf-2.7.patch6 Workaround for stricter behaviour (due to a bugfix) in 2.7,
/openbmc/openbmc/poky/meta/recipes-extended/gperf/
H A Dgperf_3.1.bb17 # it where to look explicitly (mirroring the behaviour of upstream's Makefile.devel).
/openbmc/qemu/scripts/coccinelle/
H A Dinplace-byteswaps.cocci3 // undefined behaviour if the expression being swapped is a field in a
/openbmc/u-boot/doc/
H A DREADME.ARM-memory-map1 Subject: Re: [PATCH][CFT] bring ARM memory layout in line with the documented behaviour
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-security/keyutils/files/
H A D0001-Adhere-to-the-SOURCE_DATE_EPOCH-standard.patch7 otherwise fall back to the default behaviour.
/openbmc/openbmc/poky/meta/recipes-extended/pam/libpam/pam.d/
H A Dother2 # /etc/pam.d/other - specify the PAM fallback behaviour
/openbmc/openbmc/poky/meta/recipes-extended/perl/
H A Dlibxml-sax-base-perl_1.09.bb4 PerlSAX drivers and filters. It's default behaviour is to pass \
/openbmc/docs/designs/mctp/
H A Dmctp-kernel.md154 #### Syscall behaviour
188 [Tag behaviour for transmitted messages](#tag-behaviour-for-transmitted-messages)
223 transmission. Like other `SOCK_DGRAM` behaviour, this does not generate any MCTP
245 [Tag behaviour for transmitted messages](#tag-behaviour-for-transmitted-messages)
314 allocation is lost. This tag behaviour can be controlled through the
399 ###### `MCTP_TAG_CONTROL`: manage outgoing tag allocation behaviour
410 This allows an application to control the behaviour of allocated tags for
430 Changing the default tag control behaviour should only be required when:
616 /* Set up poll behaviour, and record our starting time for
694 ##### Tag behaviour for transmitted messages
[all …]
/openbmc/openbmc-build-scripts/
H A DREADME.md15 If you see such behaviour consider [changing the thing][force-container-refresh]
/openbmc/openbmc/poky/meta/recipes-devtools/rust/rust-llvm/
H A D0001-AsmMatcherEmitter-sort-ClassInfo-lists-by-name-as-we.patch22 // accidentally rely on this behaviour, so it will have to stay like this
/openbmc/openbmc/poky/meta/recipes-devtools/clang/clang/
H A D0033-AsmMatcherEmitter-sort-ClassInfo-lists-by-name-as-we.patch22 // accidentally rely on this behaviour, so it will have to stay like this
H A D0034-llvm-config-remove-LLVM_LDFLAGS-from-ldflags-output.patch9 behaviour in llvm-config since crossscripts are not being used for
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/libconfuse/files/
H A D0001-only-apply-search-path-logic-to-relative-pathnames.patch11 This is technically an ABI change, but the current behaviour is quite
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/mraa/mraa/
H A D0001-mraa-Use-posix-basename.patch9 string to operate on to emulate GNU basename behaviour.
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-protocols/openl2tp/openl2tp/
H A Dopenl2tp-simplify-gcc-warning-hack.patch7 gcc configurations. Since the redef behaviour is essentially correct
/openbmc/openbmc/poky/meta/recipes-devtools/rsync/files/
H A Ddetermism.patch10 the output binaries. The behaviour also changes dependning on whether
/openbmc/openbmc/poky/meta/recipes-bsp/grub/files/
H A Dgrub-module-explicitly-keeps-symbole-.module_license.patch40 Upstream-Status: Inappropriate [workaround that needs investigation into @TARGET_STRIP@ behaviour i…
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/s-nail/files/
H A Dmake-errors.patch11 On top of (mk/su-find-command.sh: clearly define space behaviour)
/openbmc/openbmc/meta-arm/meta-arm/recipes-bsp/scp-firmware/files/
H A D0001-OPTEE-Private-Includes.patch9 For some reason this behaviour isn't deterministic, a ticket has been filed with upstream.

123456