| /openbmc/linux/drivers/usb/gadget/function/ |
| H A D | f_hid.c | 669 goto respond; in hidg_setup()
677 goto respond; in hidg_setup()
685 goto respond; in hidg_setup()
695 goto respond; in hidg_setup()
710 goto respond; in hidg_setup()
720 goto respond; in hidg_setup()
738 goto respond; in hidg_setup()
746 goto respond; in hidg_setup()
767 respond: in hidg_setup()
|
| /openbmc/linux/Documentation/misc-devices/ |
| H A D | eeprom.rst | 68 The other devices will not be found on a DIMM because they respond to more
80 does not respond to byte reads. If this register is present, the lower 128
83 device will no longer respond at the 0x30-37 address. The eeprom driver
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/rarpd/rarpd/ |
| H A D | 0001-rarpd.8-add-man-file.patch | 42 +) before it decides to respond to the RARP request.
62 +will not respond to the request.
|
| /openbmc/linux/net/tipc/ |
| H A D | discover.c | 210 bool respond = false; in tipc_disc_rcv() local
251 &maddr, &respond, &dupl_addr); in tipc_disc_rcv()
254 if (!respond) in tipc_disc_rcv()
|
| H A D | node.h | 96 bool *respond, bool *dupl_addr);
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-bus-fsi-devices-sbefifo | 6 timeout; i.e. the SBE did not respond within the time allotted
|
| H A D | sysfs-class-power-ltc4162l | 73 remain in this mode (and no longer respond to I2C commands)
|
| /openbmc/linux/Documentation/devicetree/bindings/rtc/ |
| H A D | isil,isl12026.txt | 4 registers respond at bus address 0x6f, and the EEPROM array responds
|
| /openbmc/openbmc/poky/meta/recipes-connectivity/nfs-utils/nfs-utils/ |
| H A D | nfs-utils-debianize-start-statd.patch | 20 # statd already running - must have been slow to respond.
|
| /openbmc/linux/Documentation/block/ |
| H A D | null_blk.rst | 76 Whether or not to use a memory buffer to respond to IO requests
80 1 Use a memory buffer to respond to IO requests
|
| /openbmc/docs/designs/ |
| H A D | bmc-reset-with-host-up.md | 69 - Both IPMI and PLDM stacks will give the host a set amount of time to respond.
122 ### Automated Recovery when host does not respond
126 host has failed to respond to any of the different mechanisms to communicate
187 on the host so it does not respond to the BMC when it comes back from its
|
| H A D | multihost-ipmi-design.md | 103 order details and respond from the command handler. This is applicable for both
166 to respond each host.The changes looks simple and no major design change from
|
| /openbmc/linux/drivers/net/wwan/iosm/ |
| H A D | iosm_ipc_mux_codec.h | 280 size_t res_size, bool blocking, bool respond);
|
| /openbmc/linux/Documentation/driver-api/xilinx/ |
| H A D | eemi.rst | 17 device to issue or respond to power management requests.
|
| /openbmc/openbmc/poky/documentation/test-manual/ |
| H A D | test-process.rst | 30 branch. If not successful, someone would respond to the changes on the
77 - QA teams respond to the email saying which tests they plan to run and
|
| /openbmc/linux/Documentation/i2c/ |
| H A D | ten-bit-addresses.rst | 8 address 0x10 (though a single device could respond to both of them).
|
| H A D | i2c-stub.rst | 16 quick commands to the specified addresses; it will respond to the other
|
| /openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/python3-jsmin/ |
| H A D | 7a75d76c2d6bfb917f30ced8f5c0a9a4157f7819.patch | 56 respond.regex = {
|
| /openbmc/linux/drivers/media/usb/dvb-usb-v2/ |
| H A D | dvbsky.c | 350 u8 command[4], respond[2], command_size, respond_size; in dvbsky_ci_ctrl() local
365 respond, respond_size); in dvbsky_ci_ctrl()
369 *mem = respond[1]; in dvbsky_ci_ctrl()
|
| /openbmc/qemu/docs/specs/ |
| H A D | pvpanic.rst | 6 management apps (e.g. libvirt) to be notified and respond to the event.
|
| /openbmc/linux/Documentation/process/ |
| H A D | 6.Followthrough.rst | 44 impulse to respond in kind. Code review is about the code, not about
66 that the reviewer is asking you to fix. And respond back to the reviewer:
184 respond to these reports is a matter of basic pride in your work. If that
216 really only one way to respond: be pleased that your problem got solved and
|
| /openbmc/docs/ |
| H A D | SECURITY.md | 26 The OpenBMC security response team (SRT) will respond to you and work to address
|
| /openbmc/linux/Documentation/w1/masters/ |
| H A D | omap-hdq.rst | 29 does not respond with a presence pulse as it does in the 1-Wire protocol.
|
| /openbmc/linux/Documentation/maintainer/ |
| H A D | feature-and-driver-maintainers.rst | 34 reviewers should try to respond quicker than what is the usual patch
81 Maintainers furthermore should respond to reports about other kinds of
|
| /openbmc/hiomapd/Documentation/ |
| H A D | mboxd.md | 42 will not respond
58 access flash without the daemon interfering. The daemon will still respond to
|