Searched full:fix (Results 1 – 25 of 200) sorted by relevance
12345678
| /Documentation/process/ |
| D | security-bugs.rst | 16 who will help verify the bug report and develop and release a fix.
17 If you already have a fix, please include it with your report, as
20 understand and fix the security vulnerability.
23 will be to diagnose and fix. Please review the procedure outlined in
34 reproduction steps, and follow it with a proposed fix, all in plain text.
42 Once a robust fix has been developed, the release process starts. Fixes
50 only valid reason for deferring the publication of a fix is to accommodate
55 order to develop a fix, such information will not be published alongside
56 the fix or on any other disclosure channel without the permission of the
81 days) start from the availability of a fix, while for "linux-distros"
[all …]
|
| D | handling-regressions.rst | 51 #. Try to fix regressions quickly once the culprit has been identified; fixes
130 the fix for backporting using the ``Cc: stable@vger.kernel.org`` tag.
177 * Aim to mainline a fix within two or three days, if the issue is severe or
181 * Aim to mainline a fix by Sunday after the next, if the culprit made it
184 resolve, try to mainline the fix within the same week.
192 merge window, except when the fix is extraordinarily risky or when the
198 dangerous way to fix a regression. Don't worry about mainlining a fixed
212 * For urgent regressions, consider asking Linus to pick up the fix straight
217 * In case you are unsure if a fix is worth the risk applying just days before
220 the fix straight from the list. He then himself can make the call and when
[all …]
|
| D | stable-kernel-rules.rst | 9 - It or an equivalent fix must already exist in Linux mainline (upstream).
15 - It must either fix a real bug that bothers people or just add a device ID.
22 be considered if they fix a notable performance or interactivity issue.
60 stable series. When doing so, ensure the fix or an equivalent is applicable,
63 e.g. a fix merged for 5.19-rc1 would be backported to 5.10.y, but not to 5.15.y.
76 it reduces the chance of accidentally exposing the fix to the public by way of
89 Cc: <stable@vger.kernel.org> # 3.3.x: fd21073: sched: Fix affinity logic
|
| D | 6.Followthrough.rst | 65 understand what the reviewer is trying to say. If possible, fix the things
66 that the reviewer is asking you to fix. And respond back to the reviewer:
167 unable to fix the regression (and nobody else does it for you), your patch
170 having a patch pulled as the result of a failure to fix a regression could
175 fix these bugs and ensure that your code's debut in a mainline kernel
176 release is as solid as possible. So, please, answer bug reports, and fix
|
| D | cve.rst | 44 If the CVE assignment team misses a specific fix that any user feels
54 the Linux kernel; assignment will only automatically happen after a fix
56 that way by the git commit id of the original fix. If anyone wishes to
|
| /Documentation/scsi/ |
| D | ChangeLog.arcmsr | 9 ** 1.10.00.10 10/10/2004 Erich Chen bug fix for SMP & ioctl
10 ** 1.20.00.00 11/29/2004 Erich Chen bug fix with arcmsr_bus_reset when PHY error
11 ** 1.20.00.02 12/09/2004 Erich Chen bug fix with over 2T bytes RAID Volume
22 ** 1.20.00.06 3/12/2005 Erich Chen fix with arcmsr_pci_unmap_dma "unsigned long" cast,
25 ** 1.20.00.07 3/23/2005 Erich Chen bug fix with arcmsr_scsi_host_template_init
29 ** bug fix enormous stack usage (Adrian Bunk's comment)
30 ** 1.20.00.08 6/23/2005 Erich Chen bug fix with abort command,
33 ** 1.20.00.09 9/12/2005 Erich Chen bug fix with abort command handling, firmware versi…
34 ** and firmware update notify for hardware bug fix
40 ** 1.20.00.11 9/29/2005 Erich Chen by comment of Arjan van de Ven fix incorrect msleep…
[all …]
|
| D | ChangeLog.ips | 43 4.70.15 - Fix Breakup for very large ( non-SG ) requests
59 4.20.13 - Fix some failure cases / reset code
65 - Fix truncation of /proc files with cat
68 4.10.13 - Fix for dynamic unload and proc file system
72 4.00.06 - Fix timeout with initial FFDC command
84 4.00.02 - Fix problem with PT DCDB with no buffer
103 0.99.05 - Fix an oops on certain passthru commands
105 0.99.04 - Fix race condition in the passthru mechanism
107 - Fix error recovery code
|
| D | ChangeLog.lpfc | 15 * Fix for issue where not all luns are seen. Search all lists
37 * Allow hex format numbers in sysfs attribute setting. Fix
73 * Merged patch from Christoph Hellwig (03/19) - fix initialization
95 * Fix compile warning/resultant panic in
134 * Fix comment for lpfc_sli_iocb_cmd_type to fit within 80 columns.
220 This will fix the free of uninitialised IRQ when config_port
225 * Fix double locking bug in the error handling part of
247 * IOCB initialization fix for Raw IO.
272 * Bug fix for Raw IO errors. Reuse of IOCBs now mandates setting
297 * Fix IOERR_RCV_BUFFER_WAITING handling for CT and ELS subsystem.
[all …]
|
| D | ChangeLog.megaraid_sas | 9 1. Fix reset_mutex leak in megasas_reset_fusion().
11 3. Fix LD/VF affiliation parsing.
23 2. Fix megasas_ioc_init_fusion to use local stack variable.
46 2. Fix the interrupt mask for Gen2 controller.
87 1. Fix Copyright dates.
105 1. Fix reglockFlags for degraded raid5/6 for MR 9360/9380.
117 3. Fix mismatch in megasas_reset_fusion() mutex lock-unlock.
130 1. Fix FastPath I/O to work with degraded RAID 1.
142 5. Fix bug where AENs could be lost in probe() and resume().
152 1. Fix some failure gotos from megasas_probe_one(), etc.
[all …]
|
| D | ChangeLog.sym53c8xx | 4 Fix sent by Stig Telfer <stig@api-networks.com>.
14 - Fix an unaligned LOAD from scripts (was used as dummy read).
24 - Fix an issue in the ncr_int_udc() (unexpected disconnect)
51 bytes was not enough for the PPR message (fix).
124 - Small fix to integrity checking code.
176 - Fix an old bug that only affected 896 rev. 1 when driver
203 - Some fix for Sparc from DSM that went directly to kernel tree.
222 - Fix up properly the PCI latency timer when needed or asked for.
226 - Fix in a tiny 'printk' bug that may oops in case of extended
270 - Fix some bug in the fully untested MDP handling:) and share
[all …]
|
| D | ChangeLog.sym53c8xx_2 | 12 - Fix a couple of printfs:
86 Fix sent by Chip Salzenberg <chip@perlsupport.com>.
88 Fix sent by Stig Telfer <stig@api-networks.com>
134 - Fix a couple of gcc/gcc3 warnings.
|
| D | ChangeLog.megaraid | 6 1. Changes in Initialization to fix kdump failure.
25 Fix: Made change in the function inserting identification mechanism
82 Fix: MegaRAID F/W has fixed the problem and being process of release,
91 Fix: A patch submitted to community from following folk.
118 > We confirmed this patch fix the problem by IA64 server.
151 Fix: Made the change in the driver so that it will return all packets
160 Could you check and get this fix in your driver?
209 2. megaraid_mbox fix: wrong order of arguments in memset()
373 i. Fix a bug in kioc's dma buffer deallocation
396 i. Fix data corruption. Because of a typo in the driver, the IO packets
[all …]
|
| /Documentation/filesystems/ |
| D | ocfs2-online-filecheck.rst | 19 log. The user can try to check/fix this file via online filecheck feature.
23 This effort is to check/fix small issues which may hinder day-to-day operations
44 input to check/fix the file.
71 2. If you determine to fix this inode, do::
73 # echo "<inode>" > /sys/fs/ocfs2/<devname>/filecheck/fix
74 # cat /sys/fs/ocfs2/<devname>/filecheck/fix
81 This time, the <ERROR> column indicates whether this fix is successful or not.
83 3. The record cache is used to store the history of check/fix results. It's
92 file metadata. In case of errors, the filesystem would fix the errors
94 the inode must first be checked for errors before performing a final fix.
|
| /Documentation/devicetree/bindings/gnss/ |
| D | mediatek.yaml | 36 gnss-fix-gpios:
38 description: GPIO used to determine device position fix state, pin names
39 FIX or 3D_FIX.
|
| /Documentation/devicetree/bindings/clock/ |
| D | amlogic,c3-pll-clkc.yaml | 27 - description: input fix pll
33 - const: fix
59 clock-names = "top", "mclk", "fix";
|
| D | amlogic,c3-peripherals-clkc.yaml | 28 - description: input fix pll
49 - const: fix
105 "fix",
|
| /Documentation/admin-guide/device-mapper/ |
| D | dm-raid.rst | 385 1.3.2 Fix/improve redundancy checking for RAID10
387 1.4.1 RAID10 fix redundancy validation checks (commit 55ebbb5).
401 1.9.1 Fix activation of existing RAID 4/10 mapped devices
407 1.10.1 Fix data corruption on reshape request
408 1.11.0 Fix table line argument order
411 1.12.1 Fix for MD deadlock between mddev_suspend() and md_write_start() available
412 1.13.0 Fix dev_health status at end of "recover" (was 'a', now 'A')
413 1.13.1 Fix deadlock caused by early md_stop_writes(). Also fix size an
415 1.13.2 Fix raid redundancy validation and avoid keeping raid set frozen
416 1.14.0 Fix reshape race on small devices. Fix stripe adding reshape
[all …]
|
| /Documentation/driver-api/firmware/ |
| D | firmware-usage-guidelines.rst | 35 * If a security fix needs lockstep firmware and kernel fixes in order to
38 should be updated with the security fix. The kernel patches should
41 both the firmware and kernel fixes. If a security fix requires
|
| /Documentation/arch/s390/ |
| D | 3270.ChangeLog | 17 Sep 2002: Fix tubfs kmalloc()s
28 Apr 2002: Fix 3270 console reboot loop
|
| /Documentation/sound/designs/ |
| D | powersave.rst | 36 power-down to the active state. These are often hardly to fix, so
37 don't report extra bug reports unless you have a fix patch ;-)
|
| /Documentation/gpu/amdgpu/display/ |
| D | display-contributing.rst | 35 is, we recommend you run all IGT tests and try to fix any failure you see in
46 Fix compilation warnings
49 Enable the W1 or W2 warning level in the kernel compilation and try to fix the
54 Fix compilation issues when using um architecture
60 area that we need to fix.
|
| /Documentation/devicetree/bindings/phy/ |
| D | xlnx,zynqmp-psgtr.yaml | 69 xlnx,tx-termination-fix:
89 xlnx,tx-termination-fix: false
|
| /Documentation/admin-guide/ |
| D | reporting-issues.rst | 72 will often be needed anyway to hunt down and fix issues.
174 switch from 5.9.15 to 5.10.5 does not qualify). The developers want to fix such
212 might not get the issue solved in older releases: the fix might be too big
219 the issue in mainline, as its commit message might tell you if the fix is
222 or peer-review possible fixes; then check the discussions if the fix was
262 the fix in the end will get incorporated in all Linux distributions.
282 will often be needed anyway to hunt down and fix issues.*
300 report and, in case it turns out to be an upstream issue, fix it directly
362 important even when a fix is prepared or in its final stages already, as
364 test a proposed fix. Jump to the section 'Duties after the report went out' for
[all …]
|
| /Documentation/arch/arm/ |
| D | mem_alignment.rst | 23 floating point emulation that works about the same way). Fix your code
41 1 The kernel will attempt to fix up the user process
|
| /Documentation/power/ |
| D | s2ram.rst | 13 simple module unload can fix it.
52 fix it, disable it, or trace into its resume function.
|
12345678