| /openbmc/linux/Documentation/process/ |
| H A D | 5.Posting.rst | 100 changes in the same patch. If a single patch fixes a critical security
176 needed additional information. If the patch fixes a bug, cite the commit
266 can be used instead of Closes: if the patch fixes a part of the issue(s)
|
| H A D | kernel-docs.rst | 168 summarizing developers' work, bug fixes, new features and versions
|
| H A D | maintainer-tip.rst | 111 Bug fixes which target mainline should always be applicable against the
413 Exceptions are made for bug fixes and *sometimes* for small standalone
418 upstream changes, fixing merge window fallout, collecting bug fixes, and
|
| H A D | researcher-guidelines.rst | 92 plenty of known bugs -- what's much more helpful is having vetted fixes.
|
| /openbmc/linux/Documentation/driver-api/ |
| H A D | console.rst | 149 and unbinding them may cause problems. With minimal fixes, these drivers can
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | gobject-introspection.rst | 66 in a cross-compilation environment. For such cases, custom-made fixes
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/android-tools/ |
| H A D | android-tools_5.1.1.r37.bb | 34 file://core/0006-adb-Musl-fixes.patch;patchdir=system/core \
|
| /openbmc/openbmc/poky/documentation/migration-guides/ |
| H A D | release-notes-4.0.5.rst | 86 …included in this release as it was built before the issues were known and fixes were available but…
|
| H A D | release-notes-3.4.3.rst | 90 - vim: Update to 8.2.4524 for further CVE fixes
|
| H A D | release-notes-4.2.1.rst | 57 - migration-guides: fixes and improvements to 4.2 release notes
|
| H A D | release-notes-4.3.4.rst | 82 - profile-manual: usage.rst: formatting fixes
|
| H A D | release-notes-4.0.7.rst | 85 - linux-yocto/5.15: ltp and squashfs fixes
|
| H A D | release-notes-4.3.2.rst | 128 - test-manual: text and formatting fixes
|
| H A D | release-notes-4.2.3.rst | 114 - ptest-runner: Pull in parallel test fixes and output handling
|
| /openbmc/qemu/docs/devel/ |
| H A D | submitting-a-patch.rst | 173 If your patch fixes a commit that is already in the repository, please
178 If your patch fixes a bug in the gitlab bug tracker, please add a line
215 your series fixes. Keeping separate commits for the test and the fix
400 If your patch fixes a severe issue or a regression, it may be applicable
|
| H A D | acpi-bits.rst | 21 This fork contains numerous fixes, a newer acpica and changes specific to
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/libeigen/libeigen/ |
| H A D | 0001-Default-eigen_packet_wrapper-constructor.patch | 13 * fixes build failures for arm targets with NEON enabled (e.g. -mfpu=neon-vfpv4)
|
| /openbmc/openbmc/poky/meta/recipes-connectivity/avahi/ |
| H A D | avahi_0.8.bb | 80 # This m4 file will get in the way of our introspection.m4 with special cross-compilation fixes
|
| /openbmc/linux/fs/ |
| H A D | Kconfig.binfmt | 37 prior bug fixes into a regression test collection. This is really
|
| /openbmc/linux/Documentation/translations/zh_TW/process/ |
| H A D | submitting-patches.rst | 165 fixes = Fixes: %h (\"%s\")
|
| /openbmc/linux/Documentation/bpf/ |
| H A D | bpf_devel_QA.rst | 119 The bpf tree itself is for fixes only, whereas bpf-next for features,
157 For fixes eventually landing in bpf -> net tree, the subject must
340 Note, fixes that go to bpf tree *must* have a ``Fixes:`` tag included.
341 The same applies to fixes that target bpf-next, where the affected
|
| /openbmc/openbmc/poky/meta/recipes-multimedia/libtiff/tiff/ |
| H A D | CVE-2023-52355-0001.patch | 5 and TIFFOpenOptionsSetMaxSingleMemAlloc() usage and some other small fixes.
|
| /openbmc/linux/Documentation/hwmon/ |
| H A D | submitting-patches.rst | 54 * Never mix bug fixes, cleanup, and functional enhancements in a single patch.
|
| /openbmc/linux/Documentation/driver-api/media/ |
| H A D | maintainer-entry-profile.rst | 196 Except for bug fixes, we don't usually add new patches to the development
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | reporting-issues.rst | 162 to any inquiries. Test proposed fixes. Do proactive testing: retest with at
222 or peer-review possible fixes; then check the discussions if the fix was
254 request fixes from developers in the upstream Linux kernel community: such
811 kernel for testing, as that where all fixes have to be applied first. Do not let
824 window fixes the issue you face; that's why you soon would have to retest with
836 Better avoid using the latest stable kernel outside merge windows, as all fixes
870 sometimes needed for debugging or testing fixes, as described later in this
1280 to any inquiries. Test proposed fixes. Do proactive testing: retest with at
1573 Some fixes are too complex
1586 to mainline. Other fixes are easy to get backported to the newest stable and
[all …]
|