| /OK3568_Linux_fs/yocto/poky/meta/classes/ |
| H A D | rm_work.bbclass | 6 # 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 D | rm_work_and_downloads.bbclass | 7 # This class is used like rm_work: 22 inherit rm_work
|
| H A D | qemuboot.bbclass | 133 # qemu-helper-native sysroot is not removed by rm_work and
|
| H A D | populate_sdk_ext.bbclass | 812 # We must avoid depending on do_build here if rm_work.bbclass is active,
|
| /OK3568_Linux_fs/yocto/poky/meta/lib/oeqa/buildperf/ |
| H A D | test_basic.py | 46 """Build core-image-sato with rm_work enabled""" 49 fobj.write('INHERIT += "rm_work"\n')
|
| /OK3568_Linux_fs/yocto/poky/meta/recipes-core/images/ |
| H A D | build-appliance-image_15.0.0.bb | 16 # 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 D | release-notes-4.0.6.rst | 137 - rm_work: exclude the SSTATETASKS from the rm_work tasks sinature 149 - sstatesig: skip the rm_work task signature
|
| H A D | release-notes-4.0.7.rst | 99 - 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/yocto/poky/meta/recipes-extended/texinfo-dummy-native/ |
| H A D | texinfo-dummy-native.bb | 21 # Using ln causes problems with rm_work
|
| /OK3568_Linux_fs/yocto/poky/meta/recipes-core/meta/ |
| H A D | wic-tools.bb | 21 # The sysroot of wic-tools is needed for wic, but if rm_work is enabled, it will
|
| /OK3568_Linux_fs/yocto/poky/meta/recipes-support/itstool/itstool/ |
| H A D | 0002-Don-t-use-build-time-hardcoded-python-binary-path.patch | 8 has INHERIT+=rm_work. Instread of hardcoding path to python binary use
|
| /OK3568_Linux_fs/yocto/meta-clang/.github/workflows/ |
| H A D | yoe.yml | 47 echo INHERIT += \"report-error rm_work\" >> conf/local.conf
|
| /OK3568_Linux_fs/yocto/poky/meta/lib/oeqa/selftest/ |
| H A D | context.py | 309 if "rm_work.bbclass" in self.tc.td["BBINCLUDED"]: 310 …self.tc.logger.error("You have rm_work enabled which isn't recommended while running oe-selftest. …
|
| /OK3568_Linux_fs/yocto/poky/scripts/contrib/ |
| H A D | convert-overrides.py | 48 …e", "task-compile", "task-install", "task-clean", "task-image-qa", "task-rm_work", "task-image-com…
|
| /OK3568_Linux_fs/kernel/include/linux/ |
| H A D | device.h | 578 * @rm_work: Work structure used for removing the link. 595 struct work_struct rm_work; member
|
| /OK3568_Linux_fs/yocto/poky/documentation/ref-manual/ |
| H A D | classes.rst | 2376 ``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 D | tasks.rst | 411 .. _ref-tasks-rm_work:
|
| H A D | variables.rst | 6345 With ``rm_work`` enabled, this variable specifies a list of recipes
|
| /OK3568_Linux_fs/yocto/poky/bitbake/ |
| H A D | ChangeLog | 234 - #1017 fix to work with rm_work
|
| /OK3568_Linux_fs/yocto/poky/meta/lib/oe/ |
| H A D | sstatesig.py | 33 # We can skip the rm_work task signature to avoid running the task
|
| /OK3568_Linux_fs/yocto/poky/bitbake/doc/bitbake-user-manual/ |
| H A D | bitbake-user-manual-metadata.rst | 771 ``buildhistory`` and ``rm_work`` classes:: 773 inherit buildhistory rm_work
|
| /OK3568_Linux_fs/kernel/drivers/base/ |
| H A D | core.c | 468 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/meta/conf/ |
| H A D | documentation.conf | 358 RM_WORK_EXCLUDE[doc] = "With rm_work enabled, this variable specifies a list of packages whose work…
|
| /OK3568_Linux_fs/yocto/poky/documentation/dev-manual/ |
| H A D | common-tasks.rst | 3378 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
|
| /OK3568_Linux_fs/yocto/poky/bitbake/lib/bb/ |
| H A D | runqueue.py | 333 rm_work are in force.
|