/openbmc/google-ipmi-sys/ |
H A D | google_accel_oob.cpp | 49 struct Reply in accelOobDeviceCount() struct 61 if (data.size_bytes() + sizeof(Reply) > MAX_IPMI_BUFFER) in accelOobDeviceCount() 67 data.size_bytes(), sizeof(Reply), MAX_IPMI_BUFFER); in accelOobDeviceCount() 73 std::vector<uint8_t> replyBuf(sizeof(Reply)); in accelOobDeviceCount() 74 auto* reply = reinterpret_cast<Reply*>(replyBuf.data()); in accelOobDeviceCount() 89 struct Reply in accelOobDeviceName() struct 102 if (data.size_bytes() + sizeof(Reply) > MAX_IPMI_BUFFER) in accelOobDeviceName() 108 data.size_bytes(), sizeof(Reply), MAX_IPMI_BUFFER); in accelOobDeviceName() 124 std::vector<uint8_t> replyBuf(data.size_bytes() + sizeof(Reply)); in accelOobDeviceName() 126 auto* reply = reinterpret_cast<Reply*>(replyBuf.data() + data.size_bytes()); in accelOobDeviceName() [all …]
|
/openbmc/google-ipmi-sys/test/ |
H A D | google_accel_oob_unittest.cpp | 38 struct Reply in TEST() struct 58 ASSERT_EQ(reply_buff.size(), sizeof(Reply)); in TEST() 60 auto* reply = reinterpret_cast<const Reply*>(reply_buff.data()); in TEST() 73 struct Reply in TEST() struct 100 ASSERT_GE(reply_buff.size(), sizeof(Reply)); in TEST() 102 auto* reply = reinterpret_cast<const Reply*>(reply_buff.data()); in TEST() 129 struct Reply in TEST() struct 161 ASSERT_GE(reply_buff.size(), sizeof(Reply)); in TEST() 163 auto* reply = reinterpret_cast<const Reply*>(reply_buff.data()); in TEST() 195 struct Reply in TEST() struct [all …]
|
/openbmc/linux/Documentation/usb/ |
H A D | usbip_protocol.rst | 158 Reply with the list of exported USB devices. 165 | 2 | 2 | 0x0005 | Reply code: The list of exported USB devices. | 248 Reply to import (attach) a remote USB device. 255 | 2 | 2 | 0x0003 | Reply code: Reply to import. | 376 Reply for submitting an URB 423 Reply for URB unlink
|
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-connectivity/bluez-tools/bluez-tools/ |
H A D | fix-memory-leaks.patch | 111 In-Reply-To: <e5db2eec2591f0109f0eb7c2631055210b55f2f5.1710791277.git.joerg.sommer@navimatix.de> 297 In-Reply-To: <e5db2eec2591f0109f0eb7c2631055210b55f2f5.1710791277.git.joerg.sommer@navimatix.de> 364 In-Reply-To: <e5db2eec2591f0109f0eb7c2631055210b55f2f5.1710791277.git.joerg.sommer@navimatix.de> 416 In-Reply-To: <e5db2eec2591f0109f0eb7c2631055210b55f2f5.1710791277.git.joerg.sommer@navimatix.de> 532 In-Reply-To: <e5db2eec2591f0109f0eb7c2631055210b55f2f5.1710791277.git.joerg.sommer@navimatix.de> 664 In-Reply-To: <e5db2eec2591f0109f0eb7c2631055210b55f2f5.1710791277.git.joerg.sommer@navimatix.de> 711 In-Reply-To: <e5db2eec2591f0109f0eb7c2631055210b55f2f5.1710791277.git.joerg.sommer@navimatix.de> 740 In-Reply-To: <e5db2eec2591f0109f0eb7c2631055210b55f2f5.1710791277.git.joerg.sommer@navimatix.de>
|
/openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-bsp/u-boot/u-boot/corstone1000/ |
H A D | 0043-firmware-psci-Fix-bind_smccc_features-psci-check.patch | 7 In-Reply-To: <20240304144242.11666-1-o451686892@gmail.com>
|
/openbmc/linux/Documentation/translations/zh_TW/process/ |
H A D | email-clients.rst | 49 郵件客戶端應該形成並且保持 References: 或者 In-Reply-To: 標題,那麼
|
H A D | submitting-patches.rst | 572 15) 明確回覆郵件頭(In-Reply-To)
|
/openbmc/linux/Documentation/translations/zh_CN/process/ |
H A D | email-clients.rst | 54 邮件客户端应该生成并且保持“References:”或者“In-Reply-To:”邮件头,这样邮件会话
|
H A D | submitting-patches.rst | 573 明确回复邮件头(In-Reply-To)
|
/openbmc/linux/drivers/message/fusion/lsi/ |
H A D | mpi_history.txt | 170 * Reply and IOC Init Request. 172 * Removed IOCFacts Reply EEDP Capability bit. 173 * 06-24-05 01.05.09 Added 5 new IOCFacts Reply IOCCapabilities bits. 561 * Modified SCSI Enclosure Processor Request and Reply to 656 * 06-30-00 01.00.04 Added Context Reply definitions per revised proposal.
|
/openbmc/linux/Documentation/process/ |
H A D | maintainer-kvm-x86.rst | 318 via ``In-Reply-To:`` headers. Using ``In-Reply-To:`` becomes an unholy mess 319 for large series and/or when the version count gets high, and ``In-Reply-To:``
|
H A D | submitting-patches.rst | 773 Explicit In-Reply-To headers 776 It can be helpful to manually add In-Reply-To: headers to a patch 780 best to avoid using In-Reply-To: to link to older versions of the
|
H A D | email-clients.rst | 48 Email clients should generate and maintain "References:" or "In-Reply-To:"
|
H A D | handling-regressions.rst | 21 loop by immediately sending at least a brief "Reply-all" with the list 69 it into the loop by sending at least a brief "Reply-all" with the list CCed;
|
H A D | maintainer-tip.rst | 798 Link tag at the end of the tag list to set the In-Reply-To email header so
|
/openbmc/qemu/nbd/ |
H A D | trace-events | 43 … const char *optname, uint32_t type, const char *typename, uint32_t len) "Reply opt=%" PRIu32 " (%…
|
/openbmc/openbmc/poky/documentation/migration-guides/ |
H A D | release-notes-4.3.1.rst | 86 - patchtest-send-results: add In-Reply-To
|
/openbmc/linux/Documentation/translations/it_IT/process/ |
H A D | submitting-patches.rst | 770 Usare esplicitamente In-Reply-To nell'intestazione 773 Aggiungere manualmente In-Reply-To: nell'intestazione dell'e-mail 777 sconsigliato l'uso di In-Reply-To: per collegare precedenti versioni.
|
H A D | email-clients.rst | 58 "References" o "In-Reply-To:" cosicché la discussione non venga interrotta.
|
/openbmc/linux/Documentation/translations/sp_SP/process/ |
H A D | submitting-patches.rst | 792 In-Reply-To explicitos en las cabeceras 795 Puede ser útil agregar manualmente encabezados In-Reply-To: a un parche 800 In-Reply-To: para vincular a versiones anteriores de la serie. De esta
|
H A D | email-clients.rst | 60 encabezados "References:" o "In-Reply-To:" para que el hilo de correo no
|
/openbmc/linux/Documentation/networking/ |
H A D | snmp_counter.rst | 207 IcmpMsgOutType8 would increase 1. And if kernel gets an ICMP Echo Reply 1065 server got ICMP Echo Reply from 8.8.8.8, so IpInReceives, IcmpInMsgs, 1066 IcmpInEchoReps and IcmpMsgInType0 were increased 1. The ICMP Echo Reply 1069 and its corresponding Echo Reply packet are constructed by:
|
H A D | ip-sysctl.rst | 1449 0 Echo Reply 1457 E Timestamp Reply 1459 G Info Reply 1461 I Address Mask Reply
|
H A D | can.rst | 806 Reply to TX_READ request (transmission task configuration). 826 Reply to RX_READ request (filter task configuration).
|
/openbmc/linux/Documentation/admin-guide/ |
H A D | reporting-regressions.rst | 402 mailing list archive and reply to it using your mailer's "Reply-all" function.
|