| /linux/Documentation/networking/device_drivers/fddi/ |
| H A D | skfp.rst | 40 Chapter 4: Describes common problems and solutions.
88 If you run into problems during installation, check those items:
180 Problems fixed:
185 Problems fixed:
202 Problems fixed:
211 Problems fixed:
216 Problems fixed:
227 Problems fixed:
237 Problems fixed:
|
| /linux/Documentation/usb/ |
| H A D | usb-serial.rst | 53 For any questions or problems with this driver, please contact
98 For any questions or problems with this driver, please contact Greg
150 For any questions or problems with the driver, please contact Ganesh
182 For any questions or problems with this driver, please contact Brian
207 For any questions or problems with this driver, please contact Hugh
221 For any questions or problems with this driver, please contact Bill Ryder.
284 If you have any questions, problems, patches, feature requests, etc. you can
289 (your problems/patches can alternately be submitted to usb-devel)
310 (alborchers@steinerpoint.com) for questions or problems with this
352 For any questions or problems with this driver, please contact William
[all …]
|
| /linux/drivers/net/wireless/ath/ath12k/ |
| H A D | Kconfig | 33 If unsure, say Y to make it easier to debug problems. But if
42 If unsure, say Y to make it easier to debug problems. But if
51 If unsure, say Y to make it easier to debug problems. But if
61 If unsure, say Y to make it easier to debug problems. But if
|
| /linux/Documentation/process/ |
| H A D | 3.Early-stage.rst | 28 the linux-kernel mailing list, where it immediately ran into problems.
89 problems like this before writing the code.
97 doors invariably has problems which are only revealed when the code is
98 released into the community. Sometimes these problems are severe,
112 deadlocks. The late revelation of these problems - and refusal to
181 posted by others. Beyond that, high-level designs often hide problems
187 Unfortunately, you also cannot assume that there are no problems with your
214 problems later. For companies without that sort of in-house expertise, the
222 This kind of review is often enough to avoid serious problems later on
|
| H A D | 1.Intro.rst | 41 avoid problems at this important stage. Developers are cautioned against
137 mainline solves a large number of distribution and support problems.
161 improved. Often review finds severe bugs and security problems. This is
204 problems, to the point that most kernel developers will not even try. So
218 problems.
258 software by its owner, or which risks creating copyright-related problems for
|
| /linux/Documentation/filesystems/ |
| H A D | locks.rst | 24 This should not cause problems for anybody, since everybody using a
31 1.2.1 Typical Problems - Sendmail
35 for example. This gave rise to some other subtle problems if sendmail was
54 fcntl(), with all the problems that implies.
|
| /linux/fs/xfs/libxfs/ |
| H A D | xfs_health.h | 23 * problems remain at unmount time, we can also request manual intervention by
37 * Evidence of health problems can be sorted into three basic categories:
43 * not themselves problems. These can be forgotten when the primary
44 * health problems are addressed.
108 /* Primary evidence of health problems in a given group. */
150 /* Secondary state related to (but not primary evidence of) health problems. */
156 /* Evidence of health problems elsewhere. */
|
| /linux/fs/xfs/ |
| H A D | xfs_sysctl.h | 23 xfs_sysctl_val_t error_level; /* Degree of reporting for problems */
39 * How much error reporting will be done when internal problems are
40 * encountered. These problems normally return an EFSCORRUPTED to their
|
| /linux/Documentation/virt/kvm/x86/ |
| H A D | timekeeping.rst | 15 4) Virtualization Problems
27 present some of the problems which arise and solutions available, giving
329 time. In practice, due to a number of problems, it is the most complicated
481 4. Virtualization Problems
491 at any time. This causes problems as the passage of real time, the injection
498 cause similar problems to virtualization makes it a good justification for
499 solving many of these problems on bare metal.
504 One of the most immediate problems that occurs with legacy operating systems
536 many problems unique to its nature as a local, potentially unstable and
582 Migration of a virtual machine raises problems for timekeeping in two ways.
[all …]
|
| /linux/Documentation/translations/zh_CN/maintainer/ |
| H A D | pull-requests.rst | 94 this in a way to successfully neutralize the problems.
96 when needed, so problems should not occur.
99 linux-next releases, and the original problems that it found have
|
| /linux/kernel/trace/rv/monitors/rtapp/ |
| H A D | rtapp.c | 15 .description = "Collection of monitors for detecting problems with real-time applications",
33 MODULE_DESCRIPTION("Collection of monitors for detecting problems with real-time applications");
|
| /linux/Documentation/maintainer/ |
| H A D | rebasing-and-merging.rst | 12 those tools incorrectly, but avoiding problems is not actually all that
18 merges would be nearly impossible. Some problems encountered by
153 also obscure problems with the development process in your tree; they can
183 pull request is a good idea. It may alert you to problems that you somehow
197 tree fails to be pulled upstream, whatever problems it had will block the
|
| /linux/drivers/net/wireless/ath/ath11k/ |
| H A D | Kconfig | 37 If unsure, say Y to make it easier to debug problems.
45 If unsure, say Y to make it easier to debug problems.
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | vidioc-log-status.rst | 32 debug problems. When this ioctl is called the driver will output the
34 dealing with problems like no sound, no video and incorrectly tuned
|
| /linux/drivers/net/wireless/ath/ath6kl/ |
| H A D | Kconfig | 43 If unsure, say Y to make it easier to debug problems.
55 If unsure, say Y to make it easier to debug problems.
|
| /linux/drivers/net/wireless/ath/wil6210/ |
| H A D | Kconfig | 44 If unsure, say Y to make it easier to debug problems.
56 If unsure, say Y to make it easier to debug problems.
|
| /linux/arch/arm/mach-pxa/ |
| H A D | sleep.S | 66 @ Intel PXA270 Specification Update notes problems sleeping
103 @ Intel PXA255 Specification Update notes problems
159 @ Intel PXA270 Specification Update notes problems performing
|
| /linux/drivers/net/wireless/ath/ath10k/ |
| H A D | Kconfig | 61 If unsure, say Y to make it easier to debug problems.
69 If unsure, say Y to make it easier to debug problems.
|
| /linux/Documentation/admin-guide/ |
| H A D | README.rst | 56 contains information about the problems, which may result by upgrading
123 you can just update packages when obvious problems arise during
153 odd problems will turn up if the configuration files are not set up
243 under some circumstances lead to problems: probing for a
255 break bad code to find kernel problems (kmalloc()). Thus you
354 If you have problems that seem to be due to kernel bugs, please follow the
|
| /linux/Documentation/admin-guide/namespaces/ |
| H A D | compatibility-list.rst | 5 This document contains the information about the problems user
8 Here's the summary. This matrix shows the known problems, that
|
| /linux/tools/testing/selftests/proc/ |
| H A D | proc-2-is-kthread.c | 31 * problems with mandatory module signing, in main()
32 * problems with lockdown mode, in main()
|
| /linux/Documentation/networking/device_drivers/ethernet/3com/ |
| H A D | vortex.rst | 18 Please report problems to one or more of:
24 Please note the 'Reporting and Diagnosing Problems' section at the end
353 Reporting and diagnosing problems
357 invaluable in resolving driver problems. We are frequently not able to
358 reproduce problems and must rely on your patience and efforts to get to
380 But for most problems it is useful to provide the following:
|
| /linux/drivers/pcmcia/ |
| H A D | o2micro.h | 128 * older bridges have problems with both read prefetch and write in o2micro_override()
156 …"O2: enabling read prefetch/write burst. If you experience problems or performance issues, use the… in o2micro_override()
163 …"O2: disabling read prefetch/write burst. If you experience problems or performance issues, use th… in o2micro_override()
|
| /linux/arch/m68k/q40/ |
| H A D | README | 45 problems. For cards using 16bit io/mem more care is required, like
66 Most problems seem to be caused by fawlty or badly configured io-cards or
130 problems, email me ideally this:
|
| /linux/Documentation/networking/ |
| H A D | batman-adv.rst | 100 Note: In order to avoid problems remove all IP addresses previously assigned to
117 When investigating problems with your mesh network, it is sometimes necessary to
145 the common diagnosis tools do not work as expected. To overcome these problems,
|