| /openbmc/linux/Documentation/target/ |
| H A D | tcmu-design.rst | 293 possibly sense_buffer), updating cmd_tail, and notifying the kernel
|
| /openbmc/linux/Documentation/powerpc/ |
| H A D | pci_iov_resource_on_powernv.rst | 288 window, we can set the PE# by updating the table that translates segments
|
| /openbmc/openbmc/poky/bitbake/doc/bitbake-user-manual/ |
| H A D | bitbake-user-manual-hello.rst | 215 ``bitbake.conf`` file (see previous example). Or, by manually updating each
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | upgrading-recipes.rst | 341 Manually updating multiple recipes scales poorly and involves many
|
| /openbmc/linux/Documentation/arch/s390/ |
| H A D | vfio-ccw.rst | 331 space, and assemble a runnable kernel channel program by updating the
|
| /openbmc/linux/Documentation/hwmon/ |
| H A D | sysfs-interface.rst | 8 This makes adding or updating support for any given chip very easy, as
|
| /openbmc/linux/Documentation/RCU/ |
| H A D | listRCU.rst | 482 a copy, updating the copy, then replacing the original with the copy.
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | reporting-issues.rst | 102 (say something broke when updating from 5.10.4 to 5.10.5), scroll down to
173 face one of those if something breaks when updating from 5.10.4 to 5.10.5 (a
437 changed in parallel to updating the kernel. The problem for example might be
578 (say something broke when updating from 5.10.4 to 5.10.5), scroll down to
615 the WiFi in your Laptop suddenly misbehaves after updating the kernel. In that
1538 line (say when updating from 5.10.4 to 5.10.5) a brief report is enough for
|
| /openbmc/qemu/docs/devel/ |
| H A D | clocks.rst | 420 Because updating a clock may trigger any side effects through
|
| H A D | build-system.rst | 417 update-buildoptions`` (or just ``make``) will take care of updating it.
|
| /openbmc/linux/Documentation/driver-api/ |
| H A D | generic-counter.rst | 330 For example, if you want to pause/unpause a Count from updating, you
|
| /openbmc/linux/tools/objtool/Documentation/ |
| H A D | objtool.txt | 269 updating the frame pointer, and CONFIG_FRAME_POINTER is enabled.
|
| /openbmc/u-boot/env/ |
| H A D | Kconfig | 135 updating the environment in flash makes it always
|
| /openbmc/openbmc/poky/meta/recipes-multimedia/libsndfile/libsndfile1/ |
| H A D | cve-2022-33065.patch | 716 ** using and updating the predictor state.
|
| /openbmc/linux/Documentation/filesystems/ |
| H A D | orangefs.rst | 522 set (bypass == 0) orangefs_inode_getattr returns without updating the inode
|
| H A D | path-lookup.rst | 440 over one component while updating ``last_type`` and ``last``. If that
619 multiple concurrent readers, the simple act of updating the count of
1235 footprints in a way that doesn't affect directories is in updating access times.
|
| /openbmc/linux/Documentation/trace/ |
| H A D | ring-buffer-design.rst | 940 will see it succeeded in updating the pointer from NORMAL to HEAD.
|
| /openbmc/linux/arch/s390/ |
| H A D | Kconfig | 799 This provides a kernel interface for creating and updating z/VM APPLDATA
|
| /openbmc/openbmc-test-automation/lib/ |
| H A D | code_update_utils.robot | 264 # contention, it may take up to 10 seconds to complete updating priority.
|
| /openbmc/linux/Documentation/RCU/Design/Data-Structures/ |
| H A D | Data-Structures.rst | 478 | of the bits with updating of the grace-period sequence number in |
857 | updating it. And if we are not going to have a single global lock, we |
|
| /openbmc/linux/Documentation/process/ |
| H A D | coding-style.rst | 354 or when updating code for an existing (as of 2020) hardware or protocol
546 - errors by not updating individual exit points when making
|
| /openbmc/openbmc/poky/documentation/toaster-manual/ |
| H A D | reference.rst | 136 Toaster is updating the layer source information.
|
| /openbmc/openbmc/poky/documentation/migration-guides/ |
| H A D | release-notes-4.3.rst | 215 regular expressions, which may mean custom patterns need updating.
|
| H A D | release-notes-4.2.rst | 57 enable updating :term:`SRC_URI` crate lists from ``Cargo.lock``
|
| /openbmc/linux/Documentation/userspace-api/netlink/ |
| H A D | intro.rst | 388 (without impacting the fast-paths updating them).
|