| /openbmc/linux/drivers/pci/hotplug/ |
| H A D | TODO | 16 * A large portion of cpqphp_ctrl.c and cpqphp_pci.c concerns resource
43 * A large portion of ibmphp_res.c and ibmphp_pci.c concerns resource
|
| /openbmc/docs/process/ |
| H A D | subproject-maintainership.md | 82 > technical leadership concerns related to OpenBMC.
124 reversed?" for each of the concerns below.
161 At least two technical concerns exist:
179 Security concerns cut both ways. It's possible that:
|
| /openbmc/docs/tof/ |
| H A D | contract.md | 11 technical leadership concerns related to OpenBMC. This source of this document
119 having security or privacy concerns, such as those involving actions of an
|
| /openbmc/linux/Documentation/scsi/ |
| H A D | sym53c500_cs.rst | 9 long overdue, and the current version addresses the following concerns:
|
| /openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/python3-uinput/ |
| H A D | 0001-Deal-with-64bit-time_t-default-on-32bit-architecture.patch | 6 Deal with Y2K38 concerns related to Linux input events on more recent
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/User/Ldap/ |
| H A D | Config.interface.yaml | 32 Currently this property is over D-bus, There are security concerns for
|
| /openbmc/linux/Documentation/devicetree/bindings/display/ |
| H A D | dsi-controller.yaml | 22 Notice: this binding concerns DSI panels connected directly to a master
|
| /openbmc/linux/drivers/gpu/drm/nouveau/nvkm/subdev/pci/ |
| H A D | g84.c | 105 /* The following only concerns PCIe cards. */ in g84_pci_init()
|
| /openbmc/linux/arch/arm64/hyperv/ |
| H A D | hv_core.c | 140 * concerns about the more verbose version.
|
| /openbmc/openbmc/poky/meta/recipes-extended/cups/ |
| H A D | cups.inc | 26 CVE_STATUS[CVE-2021-25317] = "not-applicable-config: This concerns /var/log/cups having lp ownershi…
|
| /openbmc/linux/Documentation/security/ |
| H A D | lsm.rst | 131 based on overhead, complexity and performance concerns.
|
| /openbmc/linux/Documentation/filesystems/ext4/ |
| H A D | blockgroup.rst | 83 Without the option META_BG, for safety concerns, all block group
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | LGPL-3.0-only | 61 …lar in spirit to the present version, but may differ in detail to address new problems or concerns.
|
| H A D | LGPL-3.0-or-later | 149 new problems or concerns.
|
| H A D | CERN-OHL-P-2.0 | 184 differ in detail to address new problems or concerns. New
|
| H A D | LGPL-3.0-with-zeromq-exception | 149 differ in detail to address new problems or concerns.
|
| /openbmc/linux/Documentation/process/ |
| H A D | code-of-conduct-interpretation.rst | 45 documents final escalation paths in case of unresolved concerns
|
| /openbmc/phosphor-host-ipmid/docs/ |
| H A D | contributing.md | 121 as the rest of OpenBMC. If you have any concerns, please check that document for
|
| /openbmc/docs/designs/ |
| H A D | psu-monitoring.md | 117 - Timing/serialization concerns with power supply communication.
|
| H A D | binarystore-via-blobs.md | 28 blob store and not try to write it due to concurrency concerns. It is expected
|
| /openbmc/linux/security/ |
| H A D | Kconfig | 132 Intel TXT also helps solve real end user concerns about having
|
| /openbmc/linux/tools/testing/selftests/rseq/ |
| H A D | basic_percpu_ops_test.c | 188 * rseq primitive allows us to implement pop without concerns over
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | licenses.rst | 285 One of the concerns for a development organization using open source
354 an :ref:`ref-classes-archiver` class to help avoid some of these concerns.
|
| /openbmc/linux/drivers/staging/media/atomisp/pci/isp/kernels/dvs/dvs_1.0/ |
| H A D | ia_css_dvs.host.c | 84 …o_width)); // round num_x up to blockdim_x, if it concerns the Y0Y1 block (uv_flag==0) round up to… in convert_coords_to_ispparams()
|
| /openbmc/bmcweb/ |
| H A D | DEVELOPING.md | 160 - Are there compatibility concerns? Is this change backward compatible for
|