| /openbmc/linux/arch/x86/kernel/ |
| H A D | reboot.c | 183 { /* Handle problems with rebooting on Apple MacBook5 */
191 { /* Handle problems with rebooting on Apple MacBook6,1 */
199 { /* Handle problems with rebooting on Apple MacBookPro5 */
207 { /* Handle problems with rebooting on Apple Macmini3,1 */
215 { /* Handle problems with rebooting on the iMac9,1. */
223 { /* Handle problems with rebooting on the iMac10,1. */
233 { /* Handle problems with rebooting on ASRock Q1900DC-ITX */
243 { /* Handle problems with rebooting on ASUS P4S800 */
251 { /* Handle problems with rebooting on ASUS EeeBook X205TA */
259 { /* Handle problems with rebooting on ASUS EeeBook X205TAW */
[all …]
|
| /openbmc/u-boot/tools/patman/ |
| H A D | checkpatch.py | 45 problems: List of problems, each a dict:
56 fields = ['ok', 'problems', 'errors', 'warnings', 'checks', 'lines',
62 result.problems = []
76 re_ok = re.compile('.*has no obvious style problems')
77 re_bad = re.compile('.*has style problems, please review')
89 result.problems.append(item)
155 if (len(result.problems) != result.errors + result.warnings +
157 print("Internal error: some problems lost")
158 for item in result.problems:
|
| H A D | test.py | 222 self.assertEqual(result.problems, [])
233 self.assertEqual(len(result.problems), 1)
244 self.assertEqual(len(result.problems), 1)
255 self.assertEqual(len(result.problems), 3)
266 self.assertEqual(len(result.problems), 1)
|
| /openbmc/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:
|
| /openbmc/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 …]
|
| /openbmc/u-boot/doc/ |
| H A D | README.memory-test | 1 The most frequent cause of problems when porting U-Boot to new
6 before looking for any other potential causes of any problems.
27 There are a number of serious problems with this command:
39 some problems.
90 memory problems on a specific board. The code is pretty much board
96 errors, not a single one ever. The problems this code was supposed
|
| /openbmc/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 its owner, or which risks creating copyright-related problems for the
|
| /openbmc/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.
|
| /openbmc/docs/security/ |
| H A D | obmc-security-response-team-guidelines.md | 5 problems reported by the [security vulnerability reporting process][].
13 - Keep problems private until announce.
59 3. For OpenBMC problems.
63 2. Avoid pre-announcing problems. Be especially careful with high severity
64 problems. When fixing the problem, use the contribution process but limit
75 5. Improve OpenBMC processes to avoid future problems.
138 Credit for finding these problems: ...
|
| /openbmc/openbmc/meta-ampere/meta-jade/recipes-phosphor/gpio/phosphor-gpio-monitor/ |
| H A D | ampere_psu_reset_hotswap.sh | 51 # Check FET health problems
60 echo "PSU $PSU: FET health problems have been detected"
71 echo "PSU $PSU: FET health problems have not been detected"
|
| /openbmc/linux/fs/xfs/ |
| H A D | xfs_sysctl.h | 26 xfs_sysctl_val_t error_level; /* Degree of reporting for problems */
44 * How much error reporting will be done when internal problems are
45 * encountered. These problems normally return an EFSCORRUPTED to their
|
| /openbmc/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
|
| /openbmc/openbmc/poky/documentation/profile-manual/ |
| H A D | intro.rst | 24 of problems. For help with more advanced usages and problems,
28 which we'll be continually updating as we solve more problems using the
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | CrystalStacker | 5 …for damages caused by it, though the software is not known to cause any problems. If you have trou…
7 … regarding the usability of the source but are willing to help with any problems you might run int…
|
| /openbmc/linux/drivers/net/wireless/ath/ath12k/ |
| H A D | Kconfig | 24 If unsure, say Y to make it easier to debug problems. But if
33 If unsure, say Y to make it easier to debug problems. But if
|
| /openbmc/u-boot/test/ |
| H A D | Kconfig | 23 problems. But if you are having problems with udelay() and the like,
|
| /openbmc/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 …]
|
| /openbmc/linux/drivers/net/wireless/ath/ath11k/ |
| H A D | Kconfig | 36 If unsure, say Y to make it easier to debug problems.
44 If unsure, say Y to make it easier to debug problems.
|
| /openbmc/libpldm/src/ |
| H A D | api.h | 14 * codes, which confuses the problems of the protocol with the problems of
|
| /openbmc/openbmc/poky/meta-poky/conf/distro/include/ |
| H A D | gcsections.inc | 4 # packages with build problems using sections
16 # SDK packages with build problems using sections
|
| /openbmc/google-misc/subprojects/nemora-postd/src/ |
| H A D | socket_manager.hpp | 37 * in the list. Closing a socket which is already closed causes problems.
44 * open or not. Closing a socket which is already closed causes problems.
|
| /openbmc/openbmc/poky/meta/recipes-devtools/perl/files/ |
| H A D | errno_ver.diff | 4 Subject: [PATCH] Remove Errno version check due to upgrade problems with
9 Remove version check which can cause problems for long running
|
| /openbmc/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
|
| /openbmc/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
|