| /openbmc/openbmc/meta-arm/ |
| H A D | SECURITY.md | 5 services. We operate a coordinated disclosure policy for disclosing
10 security notifications and fixes to be available and facilitate coordinated
|
| /openbmc/linux/drivers/acpi/dptf/ |
| H A D | Kconfig | 11 a coordinated approach for different policies to effect the hardware
|
| /openbmc/docs/ |
| H A D | SECURITY.md | 57 [cert guide to coordinated vulnerability disclosure]:
|
| /openbmc/docs/security/ |
| H A D | obmc-security-response-team-guidelines.md | 88 negotiate for coordinated disclosure, plan to release the fix and the security advisory
90 to coordinated disclosure), please merge the fixes (and make any private review be
96 [cert guide to coordinated vulnerability disclosure]:
|
| H A D | how-to-report-a-security-vulnerability.md | 72 [cert guide to coordinated vulnerability disclosure]:
|
| /openbmc/linux/Documentation/driver-api/media/drivers/ |
| H A D | pvrusb2.rst | 83 here. Hotplugging is ultimately coordinated here. All high level
156 glue logic which is coordinated by pvrusb2-hdw, doled out by
|
| /openbmc/linux/kernel/ |
| H A D | Kconfig.preempt | 122 This option permits Core Scheduling, a means of coordinated task
|
| /openbmc/linux/drivers/misc/ |
| H A D | vmw_balloon.c | 1189 bool coordinated) in vmballoon_deflate() argument
1251 if (coordinated) in vmballoon_deflate()
|
| /openbmc/u-boot/board/hisilicon/poplar/ |
| H A D | README | 71 having to make coordinated changes to both code bases.
|
| /openbmc/linux/Documentation/driver-api/thermal/ |
| H A D | intel_dptf.rst | 18 a coordinated approach for different policies to effect the hardware
|
| /openbmc/linux/Documentation/fb/ |
| H A D | modedb.rst | 91 and coordinated set of standard formats, display refresh rates, and
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | security-subjects.rst | 155 discuss coordinated disclosure. These mailing lists are normally non-public.
|
| /openbmc/linux/tools/power/cpupower/po/ |
| H A D | ka.po | 334 msgid " CPUs which need to have their frequency coordinated by software: "
467 " coordinated by software *\n"
|
| H A D | fr.po | 309 msgid " CPUs which need to have their frequency coordinated by software: "
438 " coordinated by software *\n"
|
| H A D | it.po | 309 msgid " CPUs which need to have their frequency coordinated by software: "
438 " coordinated by software *\n"
|
| H A D | pt.po | 308 msgid " CPUs which need to have their frequency coordinated by software: "
442 " coordinated by software *\n"
|
| H A D | cs.po | 314 msgid " CPUs which need to have their frequency coordinated by software: "
441 " coordinated by software *\n"
|
| H A D | de.po | 323 msgid " CPUs which need to have their frequency coordinated by software: "
453 " coordinated by software *\n"
|
| /openbmc/docs/designs/ |
| H A D | uart-mux-support.md | 159 un-coordinated users?
161 This is a question of policy: How those users should be coordinated will likely
|
| /openbmc/linux/Documentation/virt/kvm/x86/ |
| H A D | msr.rst | 127 coordinated between the guest and the hypervisor. Availability
|
| /openbmc/linux/Documentation/process/ |
| H A D | embargoed-hardware-issues.rst | 225 While we understand that hardware security issues need coordinated embargo
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | CAL-1.0-Combined-Work-Exception | 156 + c) You are participating in a coordinated disclosure of the
|
| H A D | CAL-1.0 | 156 + c) You are participating in a coordinated disclosure of the
|
| /openbmc/linux/Documentation/driver-api/usb/ |
| H A D | power-management.rst | 719 provided pm_qos_no_power_off is coordinated with any
789 done for 'hardwired' ports provided poweroff is coordinated with any
|
| /openbmc/linux/Documentation/networking/dsa/ |
| H A D | sja1105.rst | 379 so in a way that is coordinated with the switch port (practically, both ends of
|