| /kernel/uniproton/doc/ |
| D | contribute_guide.md | 520 7. 提交Pull Request到UniProton官方主仓库。
521 8. 查看Pull Request的状态。
607 #### **7 提交Pull Request到UniProton官方主仓库**
609 通过上述步骤，修改已经提交到个人远程仓库中，此时就可以向UniProton官方主仓库master分支提交Pull Request，该操作在gitee网页上进行。
611 1\) 进入个人账号下fork的UniProton仓库首页，点击下图红框中的“+ Pull Request”。
617 2\) 之后gitee会跳转到创建Pull Request的详细页面，并给出对应的源分支和要修改的目标分支，目标分支为UniProton官方主仓库master分支，如下图。
623 如果代码没有冲突则会显示下图红框中“可自动合并”的提示，否则需要先解决冲突然后再重新创建Pull Request。在线解决代码冲突可以参考<a href="https://gitee.com/hel…
629 填入Pull Request的标题和说明，点击“创建”，就可以提交一个Pull Request。右边的审查人员、测试人员、里程碑、标签、优先级是可选项，不选择也不影响Pull Request的创建。
636 …关联Issue</a>和<a href="https://gitee.com/help/articles/4142" target="_blank">Pull Request关联Issue</a>。
637 >- 如果提交的Pull Request中有新增意见，需要在评论里回复，并@提意见的人说明已经解决。
[all …]
|
| /kernel/linux/linux-5.10/drivers/scsi/ |
| D | hpsa.c | 1135 if (!is_firmware_flash_cmd(c->Request.CDB)) in dial_down_lockup_detection_during_fw_flash()
1144 if (is_firmware_flash_cmd(c->Request.CDB) && in dial_up_lockup_detection_on_fw_flash_complete()
2644 cp->Request.CDBLen = le16_to_cpu(c->io_flags) & in complete_scsi_command()
2648 memcpy(cp->Request.CDB, c->CDB, cp->Request.CDBLen); in complete_scsi_command()
2729 "CDB %16phN data overrun\n", cp->Request.CDB); in complete_scsi_command()
2746 cp->Request.CDB); in complete_scsi_command()
2751 cp->Request.CDB); in complete_scsi_command()
2756 cp->Request.CDB); in complete_scsi_command()
2764 cp->Request.CDB); in complete_scsi_command()
2769 cp->Request.CDB); in complete_scsi_command()
[all …]
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | cciss_ioctl.h | 12 RequestBlock_struct Request; member
20 RequestBlock_struct Request; member
|
| /kernel/linux/linux-5.10/drivers/staging/media/sunxi/cedrus/ |
| D | TODO | 2 * The Request API needs to be stabilized;
5 * Userspace support for the Request API needs to be reviewed;
|
| /kernel/linux/linux-5.10/Documentation/crypto/ |
| D | api-aead.rst | 16 Asynchronous AEAD Request Handle
20 :doc: Asynchronous AEAD Request Handle
|
| D | api-skcipher.rst | 19 Symmetric Key Cipher Request Handle
23 :doc: Symmetric Key Cipher Request Handle
|
| D | api-digest.rst | 19 Asynchronous Hash Request Handle
23 :doc: Asynchronous Hash Request Handle
|
| D | api-akcipher.rst | 16 Asymmetric Cipher Request Handle
|
| D | api-kpp.rst | 16 Key-agreement Protocol Primitives (KPP) Cipher Request Handle
|
| /kernel/linux/linux-5.10/drivers/media/mc/ |
| D | Kconfig | 21 This option enables the Request API for the Media controller and V4L2
27 comment "Please notice that the enabled Media controller Request API is EXPERIMENTAL"
|
| /kernel/linux/linux-5.10/Documentation/networking/ |
| D | ethtool-netlink.rst | 45 Request header
288 Request contents:
344 Request contents:
374 Request contents:
394 Request contents:
424 Request contents:
455 Request contents:
603 Request contents:
633 Request contents:
651 Request contents:
[all …]
|
| D | can_ucan_protocol.rst | 71 Request the device firmware string.
122 Request the device information structure ``ucan_ctl_payload_t.device_info``.
133 Request the device protocol version
|
| /kernel/linux/patches/linux-5.10/prebuilts/usr/include/linux/ |
| D | cciss_ioctl.h | 47 RequestBlock_struct Request; member
54 RequestBlock_struct Request; member
|
| /kernel/linux/linux-5.10/include/uapi/linux/ |
| D | cciss_ioctl.h | 43 RequestBlock_struct Request; member
51 RequestBlock_struct Request; member
|
| /kernel/linux/patches/linux-4.19/prebuilts/usr/include/linux/ |
| D | cciss_ioctl.h | 36 RequestBlock_struct Request; member
43 RequestBlock_struct Request; member
|
| /kernel/linux/linux-5.10/Documentation/block/ |
| D | request.rst | 57 int rq_status D Request status bits
96 ``struct request_queue *q`` DB Request queue this request belongs to
98 ``struct request_list *rl`` B Request list this request came from
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/mediactl/ |
| D | request-api.rst | 6 Request API
9 The Request API has been designed to allow V4L2 to deal with requirements of
19 Supporting these features without the Request API is not always possible and if
26 The Request API allows a specific configuration of the pipeline (media
36 The Request API extends the Media Controller API and cooperates with
45 Request Allocation
52 Request Preparation
62 Request Submission
162 Note that it is not allowed to use the Request API for CAPTURE buffers
|
| D | media-func-ioctl.rst | 59 Request-specific error codes are listed in the individual requests
|
| /kernel/linux/linux-5.10/drivers/staging/media/ipu3/ |
| D | TODO | 4 - Request API conversion. Remove of the dual pipeline and associate buffers
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/media/ |
| D | intro.rst | 26 - Video4Linux Request API (experimental);
|
| /kernel/linux/common_modules/ |
| D | README.en.md | 26 4. Create Pull Request
|
| /kernel/linux/linux-5.10/drivers/message/fusion/lsi/ |
| D | mpi_history.txt | 80 * Added define for offset of High Priority Request Queue.
170 * Reply and IOC Init Request.
203 * 05-24-07 01.05.14 Added Common Boot Block type to FWDownload Request.
204 * Added Common Boot Block type to FWUpload Request.
557 * 01-15-05 01.05.03 Modified SCSI Enclosure Processor Request to support
559 * 03-11-05 01.05.04 Removed EEDP flags from SCSI IO Request.
560 * Removed SCSI IO 32 Request.
561 * Modified SCSI Enclosure Processor Request and Reply to
571 * Request: Do Not Send Task IU and Soft Reset Option.
614 * 03-11-05 01.05.04 Removed TargetAssistExtended Request.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/scsi/ |
| D | arcmsr_spec.rst | 61 Request frame must be 32 bytes aligned:
83 Request reply:
108 Request frame is sent from configuration space:
111 offset: 0x78 Request Frame (bit30 == 1)
137 Request len 0x00000200(4)
156 UPPER32 of Request Frame (4)-->Driver Only
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-bus-pci-devices-aer_stats | 55 Unsupported Request 0
85 Unsupported Request 0
|
| /kernel/linux/linux-5.10/Documentation/x86/ |
| D | intel-iommu.rst | 105 DMAR:[DMA Write] Request device [00:02.0] fault addr 6df084000
107 DMAR:[DMA Write] Request device [00:02.0] fault addr 6df084000
|