| /openbmc/openbmc/meta-raspberrypi/docs/ |
| H A D | contributing.md | 10 Feel free to ask any kind of questions but please always prepend your email
38 * For changes that affect *layer recipes*, please just use the **base names**
43 * For changes that affect the *layer documentation*, please just use `docs`
46 please use the full path as the component name, e.g. `conf/layer.conf`.
48 the above cases, please use `meta-raspberrypi` as the component name.
69 A common issue during patch reviewing is commit log formatting, please review
80 mailing list. In this case, when creating patches using `git` please make
100 If you submit patches that have a GitHub issue associated, please make sure to
|
| /openbmc/u-boot/cmd/mvebu/ |
| H A D | Kconfig | 9 For details about bubt command please see the documentation
22 For details about bubt command please see the documentation
31 For details about bubt command please see the documentation
40 For details about bubt command please see the documentation
|
| /openbmc/u-boot/doc/ |
| H A D | README.nios2 | 4 Please refer to the link for more information on Nios II,
7 Please refer to the link for Linux port and toolchains,
10 The Nios II port of u-boot is controlled by device tree. Please check
26 using the sopc2dts tool. Then modified to fit your configuration. Please
32 You will need to add additional properties to the dts. Please find an
79 Please change the SDRAM base and size to match your board. The base
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/epeg/epeg/ |
| H A D | 0001-configure-Fix-checks-for-libjpeg-and-libexif.patch | 23 -AC_CHECK_LIB([jpeg], [main], [], [echo "libjpeg library not found. Please install it before procee…
24 -AC_CHECK_LIB([exif], [main], [], [echo "libexif library not found. Please install it before procee…
25 +AC_CHECK_LIB([jpeg], [jpeg_simple_progression], [], [echo "libjpeg library not found. Please insta…
26 +AC_CHECK_LIB([exif], [exif_data_new_from_file], [], [echo "libexif library not found. Please insta…
|
| /openbmc/bmcweb/.github/ISSUE_TEMPLATE/ |
| H A D | bug_report.yml | 14 …To report a security vulnerability, please follow <https://github.com/openbmc/docs/blob/master/sec…
16 … To ask questions about how to use OpenBMC, please visit <https://discord.gg/69Km47zH98>.
43 Include the contents of /etc/os-release. Please ensure that the
54 …Please ensure you have collected the relevant debugging information manually and attached below; …
|
| H A D | config.yml | 4 about: "Please file any feature requests to the main openbmc project."
8 "Please file any bug causing a crash to
|
| /openbmc/u-boot/doc/driver-model/ |
| H A D | pmic-framework.txt | 91 For detailed API description, please refer to the header file.
93 As an example of the pmic driver, please refer to the MAX77686 driver.
95 Please pay attention for the driver's bind() method. Exactly the function call:
110 For more information, please refer to the core file.
127 For detailed API description, please refer to the header file.
129 For the example regulator driver, please refer to the MAX77686 regulator driver,
140 For more information, please refer to the command file.
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | CrystalStacker | 1 …ed you include this document in it's original form in your distribution. Please see the "Contactin…
7 …please provided that you include this file in its unmodified form with any new distribution. NewCr…
|
| /openbmc/openbmc/poky/meta/recipes-extended/bash/bash/ |
| H A D | run-ptest | 9 echo "Warning: The en_US* locales is needed to run the intl.tests, please add it."
14 echo "Warning: The fr_FR* locales is needed to run the intl.tests, please add it."
19 echo "Warning: The de_DE* locales is needed to run the intl.tests, please add it."
|
| /openbmc/openbmc-test-automation/ipmi/ |
| H A D | test_ipmi_kcs.robot | 40 Should Not Be Empty ${OS_HOST} msg=Please provide required parameter OS_HOST
41 Should Not Be Empty ${OS_USERNAME} msg=Please provide required parameter OS_USERNAME
42 Should Not Be Empty ${OS_PASSWORD} msg=Please provide required parameter OS_PASSWORD
|
| /openbmc/openbmc/.github/ISSUE_TEMPLATE/ |
| H A D | bug_report.md | 11 Please note that questions or feature requests should be discussed on the
12 mailing list or Discord. Please see https://github.com/openbmc/openbmc#contact
14 only. Please remove this section when opening a bug.
|
| /openbmc/openbmc/poky/meta/classes-global/ |
| H A D | sanity.bbclass | 52 local.conf.sample and there have been updates made to this file. Please compare the two
72 site.conf.sample and there have been updates made to this file. Please compare the two
93 Please compare your file against bblayers.conf.sample and merge any changes before continuing.
289 …return "Failed to create a file with a long name in %s. Please use a filesystem that does not unre…
299 …return "The length of %s is longer than %s, this would cause unexpected errors, please use a short…
364 msg += " Please ensure your host's network is configured correctly.\n"
365 … msg += " Please ensure CONNECTIVITY_CHECK_URIS is correct and specified URIs are available.\n"
402 …messages = messages + 'TUNE_ARCH is unset. Please ensure your MACHINE configuration includes a val…
406 …messages = messages + 'Please set TARGET_OS directly, or choose a MACHINE or DISTRO that does so.\…
441 …version of patch is older than 2.7 and has bugs which will break builds. Please install a newer ve…
[all …]
|
| /openbmc/openbmc-test-automation/docs/ |
| H A D | gui_setup_reference.md | 38 - Python Installation: Please follow the documented procedure available.
40 - Firefox Installation: Please follow the documented procedure available.
42 - geckodriver installation: Please follow the documented procedure available.
|
| /openbmc/u-boot/doc/device-tree-bindings/mtd/ |
| H A D | altera_qspi.txt | 17 - #address-cells: please refer to /mtd/partition.txt
18 - #size-cells: please refer to /mtd/partition.txt
19 For partitions inside each flash, please refer to /mtd/partition.txt
|
| /openbmc/openbmc/meta-openembedded/meta-networking/ |
| H A D | MAINTAINERS | 3 Please submit any patches against meta-networking to the OpenEmbedded
7 When sending single patches, please use something like:
24 Please keep this list in alphabetical order.
|
| /openbmc/phosphor-misc/ |
| H A D | README.md | 16 Please submit patches to Gerrit. More information on using Gerrit can be found
22 Patch checklist. Please ensure patches adhere to the following guidelines:
27 For questions or help please come join us on the
|
| /openbmc/u-boot/.github/ |
| H A D | pull_request_template.md | 1 Please do not submit a Pull Request via github. Our project makes use of
2 mailing lists for patch submission and review. For more details please
|
| /openbmc/openbmc/.github/ |
| H A D | pull_request_template.md | 1 Please do not submit a Pull Request via github. Our project makes use of
2 Gerrit for patch submission and review. For more details please
|
| /openbmc/openbmc/poky/scripts/contrib/ |
| H A D | dialog-power-control | 22 PROMPT="Please turn device power on";;
24 PROMPT="Please turn device power off";;
26 PROMPT="Please click Done, then turn the device power off then on";;
|
| /openbmc/openbmc/meta-aspeed/ |
| H A D | README.md | 22 Please submit patches to Gerrit. More information on using Gerrit can be found
27 Patch checklist. Please ensure patches adhere to the following guidelines:
34 For questions or help please come join us on the [mailing
|
| /openbmc/openbmc/meta-arm/ |
| H A D | SECURITY.md | 17 number), please contact the meta-arm mailing list at
20 If you are dealing with a not-yet released or urgent issue, please send a mail
24 For more information, please visit https://developer.arm.com/support/arm-security-updates/report-se…
|
| H A D | README.md | 38 To interact with the meta-arm developer community, please email the meta-arm mailing list at <meta-…
40 To subscribe to the meta-arm mailing list, please go to
46 information on how to submit a patch, please read
78 …logy, schedule, and stable/LTS support timelines. For more information on these, please reference:
92 For information on the security of meta-arm and how to report issues, please consult [SECURITY.md](…
|
| /openbmc/openbmc/meta-raspberrypi/.github/ |
| H A D | PULL_REQUEST_TEMPLATE.md | 2 Please make sure you've read and understood our contributing guidelines.
11 Please provide the following information:
|
| /openbmc/openbmc/meta-openpower/ |
| H A D | README.md | 34 Please submit patches to Gerrit. More information on using Gerrit can be found
39 Patch checklist. Please ensure patches adhere to the following guidelines:
46 For questions or help please come join us on the [mailing
|
| /openbmc/docs/security/ |
| H A D | how-to-report-a-security-vulnerability.md | 27 Please note the OpenBMC project has multiple source code repositories. Each has
55 Please refer to the [CERT Guide to Coordinated Vulnerability Disclosure][],
60 - If the problem is not severe, please write an issue to the affected repository
65 version of OpenBMC), please report it and we will help you route it to the
|