Home
last modified time | relevance | path

Searched refs:rm_work (Results 1 – 18 of 18) sorted by relevance

/OK3568_Linux_fs/yocto/poky/meta/classes/
H A Drm_work.bbclass6 # INHERIT += "rm_work"
8 # To inhibit rm_work for some recipes, specify them in RM_WORK_EXCLUDE.
22 # Use the completion scheduler by default when rm_work is active
26 # Run the rm_work task in the idle scheduling class
27 BB_TASK_IONICE_LEVEL:task-rm_work = "3.0"
40 bbnote "rm_work: Skipping ${PN} since it is in RM_WORK_EXCLUDE"
138 # without also invoking do_rm_work. It only exists when rm_work.bbclass
H A Drm_work_and_downloads.bbclass7 # This class is used like rm_work:
22 inherit rm_work
H A Dqemuboot.bbclass133 # qemu-helper-native sysroot is not removed by rm_work and
H A Dpopulate_sdk_ext.bbclass812 # We must avoid depending on do_build here if rm_work.bbclass is active,
/OK3568_Linux_fs/yocto/poky/meta/recipes-extended/texinfo-dummy-native/
H A Dtexinfo-dummy-native.bb21 # Using ln causes problems with rm_work
/OK3568_Linux_fs/yocto/poky/meta/recipes-support/itstool/itstool/
H A D0002-Don-t-use-build-time-hardcoded-python-binary-path.patch8 has INHERIT+=rm_work. Instread of hardcoding path to python binary use
/OK3568_Linux_fs/yocto/poky/meta/recipes-core/meta/
H A Dwic-tools.bb21 # The sysroot of wic-tools is needed for wic, but if rm_work is enabled, it will
/OK3568_Linux_fs/yocto/poky/meta/recipes-core/images/
H A Dbuild-appliance-image_15.0.0.bb16 # Ensure there's enough space to do a core-image-sato build, with rm_work enabled
64 echo "INHERIT += \"rm_work\"" >> ${IMAGE_ROOTFS}/home/builder/poky/build/conf/auto.conf
/OK3568_Linux_fs/yocto/poky/documentation/migration-guides/
H A Drelease-notes-4.0.6.rst137 - rm_work: exclude the SSTATETASKS from the rm_work tasks sinature
149 - sstatesig: skip the rm_work task signature
H A Drelease-notes-4.0.7.rst99 - rm_work.bbclass: use HOSTTOOLS 'rm' binary exclusively
100 - rm_work: adjust dependency to make do_rm_work_all depend on do_rm_work
/OK3568_Linux_fs/kernel/include/linux/
H A Ddevice.h595 struct work_struct rm_work; member
/OK3568_Linux_fs/kernel/drivers/base/
H A Dcore.c468 struct device_link *link = container_of(work, struct device_link, rm_work); in device_link_release_fn()
485 INIT_WORK(&link->rm_work, device_link_release_fn); in devlink_dev_release()
492 queue_work(system_long_wq, &link->rm_work); in devlink_dev_release()
/OK3568_Linux_fs/yocto/poky/documentation/ref-manual/
H A Dclasses.rst2376 ``rm_work.bbclass``
2379 The ``rm_work`` class supports deletion of temporary workspace, which
2389 build progresses, you can enable ``rm_work`` by adding the following to
2393 INHERIT += "rm_work"
2397 recipe, enabling ``rm_work`` will potentially result in your changes to
2399 directories deleted by ``rm_work``, you can add the names of the recipe
H A Dtasks.rst411 .. _ref-tasks-rm_work:
H A Dvariables.rst6345 With ``rm_work`` enabled, this variable specifies a list of recipes
/OK3568_Linux_fs/yocto/poky/bitbake/
H A DChangeLog234 - #1017 fix to work with rm_work
/OK3568_Linux_fs/yocto/poky/bitbake/doc/bitbake-user-manual/
H A Dbitbake-user-manual-metadata.rst771 ``buildhistory`` and ``rm_work`` classes::
773 inherit buildhistory rm_work
/OK3568_Linux_fs/yocto/poky/documentation/dev-manual/
H A Dcommon-tasks.rst3378 recipe or have ``rm_work`` enabled, the
3427 Modifications will also disappear if you use the ``rm_work`` feature as
4628 :ref:`rm_work <ref-classes-rm-work>` class:
6505 INHERIT += "rm_work"
6509 "rm_work", see the
6510 :ref:`rm_work <ref-classes-rm-work>` class in the
9360 :ref:`rm_work <ref-classes-rm-work>` is not