| /openbmc/docs/security/ |
| H A D | network-security-considerations.md | 9 a security vulnerability, please consider [how to report a security vulnerability][].
11 [how to report a security vulnerability]:
12 https://github.com/openbmc/docs/blob/master/security/how-to-report-a-security-vulnerability.md
|
| /openbmc/bmcweb/redfish-core/lib/ |
| H A D | trigger.hpp | 821 nlohmann::json::object_t report; in getMetricReportDefinitions() local
822 report["@odata.id"] = boost::urls::format( in getMetricReportDefinitions()
825 reports.emplace_back(std::move(report)); in getMetricReportDefinitions()
|
| /openbmc/linux/Documentation/sound/hd-audio/ |
| H A D | notes.rst | 127 driver to probe the codec slots the hardware doesn't report for use.
146 defined in hda_intel.c. In such a case, please report and give the
239 Before making a bug report, double-check whether the mixer is set up
255 report. See the bug report section for details.
278 Thus, before submitting a bug report, make sure that you set up the
706 to send a bug report to the developers. Give the following in your
707 bug report:
718 Send a bug report either the following:
748 on alsa-project.org. But, if you send a bug report, it'd be better to
|
| /openbmc/linux/Documentation/networking/ |
| H A D | xfrm_sync.rst | 165 iii) kernel->user to report as event if someone sets any values or
171 iv) kernel->user to report event when replay threshold or a timeout
|
| /openbmc/linux/Documentation/admin-guide/laptops/ |
| H A D | asus-laptop.rst | 70 bug report to do, please include the output of this entry.
259 Please include the following information in your report:
|
| /openbmc/linux/Documentation/sound/designs/ |
| H A D | procfile.rst | 185 And if that makes your HDMI audio work, please report to us so that we
217 If it's really a bug, report it with the following information:
|
| /openbmc/openbmc/meta-arm/meta-arm-systemready/ |
| H A D | README.md | 40 report files through the use of the [EDK2 SCT Results Parser][] and the
48 which generates report files and analyzes the test results.
|
| /openbmc/openbmc/poky/documentation/ref-manual/ |
| H A D | resources.rst | 48 - The ":doc:`../contributor-guide/report-defect`"
189 you should report them using this application.
|
| /openbmc/linux/Documentation/hwmon/ |
| H A D | lm80.rst | 59 Voltage sensors (also known as IN sensors) report their values in volts.
|
| /openbmc/linux/Documentation/devicetree/bindings/input/ |
| H A D | brcm,bcm-keypad.txt | 6 The keypad controller can sense a key-press and key-release and report the
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-security/nmap/files/ |
| H A D | 0002-Fix-building-with-libc.patch | 61 …warning(QT_2, "Bogus field specifier found in client #%d context. Please report a bug", ctx->getId…
|
| /openbmc/linux/Documentation/filesystems/ |
| H A D | udf.rst | 8 please report them according to MAINTAINERS file.
|
| /openbmc/linux/Documentation/devicetree/bindings/crypto/ |
| H A D | fsl,sec-v4.0-mon.yaml | 83 by SNVS ONOFF, the driver can report the status of POWER key and wakeup
|
| /openbmc/linux/sound/soc/ti/ |
| H A D | omap-twl4030.c | 134 .report = SND_JACK_HEADSET,
|
| /openbmc/linux/drivers/hid/ |
| H A D | hid-letsketch.c | 166 struct hid_report *report, in letsketch_raw_event() argument
|
| H A D | hid-cougar.c | 257 static int cougar_raw_event(struct hid_device *hdev, struct hid_report *report, in cougar_raw_event() argument
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | filesystem-monitoring.rst | 25 problem. For this reason, FAN_FS_ERROR tries to report only the first
|
| /openbmc/phosphor-led-manager/fault-monitor/ |
| H A D | fru-fault-monitor.cpp | 98 report<InvalidArgumentErr>( in action()
|
| /openbmc/docs/designs/ |
| H A D | event-logging.md | 144 report<InvalidCertificate>(Reason("Existing certificate file is corrupted"));
151 `elog` and `report` have slightly different behaviors: `elog` throws an
153 elsewhere in the application, while `report` sends the event directly to
195 the `systemd` journal on each error report, which limits scalability.
208 - Applications running on the BMC must be able to report errors and failure
228 - Applications running on the BMC should be able to report important tracing
241 report their own errors and events. Examples of managed entities would be
559 // Immediately report the event:
|
| H A D | gpio-based-cable-presence.md | 9 The intent of this new daemon design is to report GPIO-based cable presence
169 group. Meanwhile, only the zero bit is used to report the presence state.
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-devices-edac | 53 field should be monitored for non-zero values and report
149 and report such information to the system administrator.
|
| /openbmc/linux/Documentation/admin-guide/device-mapper/ |
| H A D | statistics.rst | 78 nanoseconds. For each range, the kernel will report the
81 report four numbers a:b:c:d. a is the number of requests
|
| /openbmc/linux/drivers/input/mouse/ |
| H A D | elan_i2c_i2c.c | 729 u8 *report, unsigned int report_len) in elan_i2c_get_report() argument
733 len = i2c_master_recv(client, report, report_len); in elan_i2c_get_report()
|
| /openbmc/openbmc/poky/meta/recipes-support/lzop/lzop/ |
| H A D | acinclude.m4 | 84 AC_MSG_NOTICE([a patch or bug-report to <${PACKAGE_BUGREPORT}>.])
151 AC_MSG_NOTICE([a patch or bug-report to <${PACKAGE_BUGREPORT}>.])
|
| /openbmc/linux/Documentation/fb/ |
| H A D | sstfb.rst | 20 Please read the Bug section, and report any success or failure to me
39 drop me a report :)
|