Home
last modified time | relevance | path

Searched refs:fixes (Results 1 – 25 of 391) sorted by relevance

12345678910>>...16

/openbmc/linux/drivers/mmc/host/
H A Dsdhci-pci-core.c2004 if (chip->fixes && chip->fixes->suspend) in sdhci_pci_suspend()
2005 return chip->fixes->suspend(chip); in sdhci_pci_suspend()
2017 if (chip->fixes && chip->fixes->resume) in sdhci_pci_resume()
2018 return chip->fixes->resume(chip); in sdhci_pci_resume()
2032 if (chip->fixes && chip->fixes->runtime_suspend) in sdhci_pci_runtime_suspend()
2033 return chip->fixes->runtime_suspend(chip); in sdhci_pci_runtime_suspend()
2045 if (chip->fixes && chip->fixes->runtime_resume) in sdhci_pci_runtime_resume()
2046 return chip->fixes->runtime_resume(chip); in sdhci_pci_runtime_resume()
2071 if (chip->fixes && chip->fixes->cd_gpio_override) in sdhci_pci_add_gpio_lookup_table()
2072 dmi_id = dmi_first_match(chip->fixes->cd_gpio_override); in sdhci_pci_add_gpio_lookup_table()
[all …]
/openbmc/linux/Documentation/fb/
H A Dcirrusfb.rst60 * Bug fixes.
69 * Compile fixes related to new 2.3.x IORESOURCE_IO[PORT] symbol changes.
76 * Casting fixes.
78 * Bug fixes.
/openbmc/openbmc/meta-arm/
H A DSECURITY.md10 security notifications and fixes to be available and facilitate coordinated
27 ## Branches maintained with security fixes
43 pull upstream components, incorporating their respective security fixes
45 components they use contain all the required security fixes, if and when they
/openbmc/linux/Documentation/admin-guide/cifs/
H A Dauthors.rst42 - Kazeon team for various fixes especially for 2.4 version.
47 - Jeff Layton (many, many fixes, as well as great work on the cifs Kerberos code)
50 - Aurelien Aptel (for DFS SMB3 work and some key bug fixes)
51 - Ronnie Sahlberg (for SMB3 xattr work, bug fixes, and lots of great work on compounding)
53 - Sachin Prabhu (many bug fixes, including for reconnect, copy offload and security)
/openbmc/linux/Documentation/driver-api/firmware/
H A Dfirmware-usage-guidelines.rst22 fixes/changes. The firmware files in linux-firmware should be
35 * If a security fix needs lockstep firmware and kernel fixes in order to
40 is fixed. All communications around security fixes should point at
41 both the firmware and kernel fixes. If a security fix requires
/openbmc/openbmc/meta-arm/meta-arm-bsp/documentation/corstone1000/
H A Dindex.rst15 pull upstream components, incorporating their respective security fixes
17 components they use contain all the required security fixes, if and when they
/openbmc/openbmc/poky/scripts/pybootchartgui/
H A DNEWS5 + Robustness fixes to taskstats and meminfo parsing
6 + More python3 fixes
15 + More python3 fixes
41 + python3 compatibility fixes (Riccardo)
45 + lot of fixes for easier packaging (Peter Hjalmarsson)
102 + README fixes (xrmx, Michael)
191 + initrd portability & fixes (Federic Crozat)
/openbmc/linux/drivers/staging/vt6656/
H A DTODO14 - checkpatch.pl fixes
15 - sparse fixes
/openbmc/linux/drivers/staging/vt6655/
H A DTODO16 - checkpatch.pl fixes
17 - sparse fixes
/openbmc/openbmc/meta-security/meta-tpm/recipes-tpm2/ibmswtpm2/files/
H A Dtune-makefile.patch3 fixes:
11 fixes:
/openbmc/u-boot/lib/lzma/
H A Dhistory.txt41 - Some minor fixes
46 - Some minor fixes
60 - Some minor fixes.
169 - Small fixes in C++ code
174 - Small fixes
/openbmc/openbmc/poky/meta/recipes-connectivity/bluez5/
H A Dbluez5_5.79.bb5 CVE_STATUS[CVE-2020-24490] = "cpe-incorrect: This issue has kernel fixes rather than bluez fixes"
/openbmc/openbmc/poky/meta/recipes-extended/unzip/unzip/
H A DCVE-2021-4217.patch6 This fixes a bug that causes use of uninitialized heap data if `readbuf` fails
8 Furthermore, this fixes a null pointer dereference if an archive contains an
/openbmc/linux/drivers/net/dsa/mv88e6xxx/
H A Dpcs-639x.c678 } fixes[] = { in mv88e6393x_erratum_5_2() local
690 for (i = 0; i < ARRAY_SIZE(fixes); ++i) { in mv88e6393x_erratum_5_2()
691 err = mdiodev_c45_modify(&mpcs->mdio, fixes[i].dev, in mv88e6393x_erratum_5_2()
692 fixes[i].reg, fixes[i].mask, in mv88e6393x_erratum_5_2()
693 fixes[i].val); in mv88e6393x_erratum_5_2()
/openbmc/phosphor-state-manager/subprojects/
H A Dcereal.wrap4 # need at least for C++20 fixes 3e4d1b84cab4891368d2179a61a7ba06a5693e7f
/openbmc/phosphor-logging/subprojects/
H A Dcereal.wrap4 # need at least for C++20 fixes 3e4d1b84cab4891368d2179a61a7ba06a5693e7f
/openbmc/openpower-occ-control/subprojects/
H A Dcereal.wrap4 # need at least for C++20 fixes 3e4d1b84cab4891368d2179a61a7ba06a5693e7f
/openbmc/phosphor-user-manager/subprojects/
H A Dcereal.wrap4 # need at least for C++20 fixes 3e4d1b84cab4891368d2179a61a7ba06a5693e7f
/openbmc/phosphor-led-manager/subprojects/
H A Dcereal.wrap4 # need at least for C++20 fixes 3e4d1b84cab4891368d2179a61a7ba06a5693e7f
/openbmc/phosphor-post-code-manager/subprojects/
H A Dcereal.wrap4 # need at least for C++20 fixes 3e4d1b84cab4891368d2179a61a7ba06a5693e7f
/openbmc/phosphor-bmc-code-mgmt/subprojects/
H A Dcereal.wrap4 # need at least for C++20 fixes 3e4d1b84cab4891368d2179a61a7ba06a5693e7f
/openbmc/phosphor-debug-collector/subprojects/
H A Dcereal.wrap4 # need at least for C++20 fixes 3e4d1b84cab4891368d2179a61a7ba06a5693e7f
/openbmc/linux/drivers/staging/rts5208/
H A DTODO3 - checkpatch.pl fixes
/openbmc/linux/drivers/gpu/drm/ci/
H A Dbuild.sh63 git pull ${UPSTREAM_REPO} ${TARGET_BRANCH}-external-fixes
69 git pull origin ${TARGET_BRANCH}-external-fixes
/openbmc/linux/Documentation/process/
H A Dmaintainer-kvm-x86.rst27 Generally speaking, fixes for the current cycle are applied directly to the
30 through the KVM x86 tree, it will be applied to the ``fixes`` branch before
45 All topic branches, except for ``next`` and ``fixes``, are rolled into ``next``
61 close around rc5 for new features, and a soft close around rc6 for fixes (for
62 the next release; see above for fixes that target the current release).
88 ``git://git.kernel.org/pub/scm/virt/kvm/kvm.git master``. Note, fixes do not
90 rule, but typically only fixes for bugs that are urgent, critical, and/or were
228 If a change fixes a KVM/kernel bug, add a Fixes: tag even if the change doesn't
229 need to be backported to stable kernels, and even if the change fixes a bug in
296 Except for "obvious" found-by-inspection bugs, fixes must be accompanied by a
[all …]

12345678910>>...16