Searched refs:submitter (Results 1 – 13 of 13) sorted by relevance
72 struct submitter { struct93 static struct submitter submitters[1]; argument107 static int io_uring_register_buffers(struct submitter *s) in io_uring_register_buffers()116 static int io_uring_register_files(struct submitter *s) in io_uring_register_files()138 static unsigned file_depth(struct submitter *s) in file_depth()143 static void init_io(struct submitter *s, unsigned index) in init_io()244 static int reap_events(struct submitter *s) in reap_events()280 struct submitter *s = data; in submitter_fn()389 static int setup_ring(struct submitter *s) in setup_ring()464 struct submitter *s = &submitters[0]; in file_depths()[all …]
9 rule (c) of the developers certificate of origin, you should ask the submitter25 and protect the submitter from complaints. Note that under no circumstances
57 opening. Clarify for the submitter the key dates (in terms of -rc release
93 enum scsi_cmnd_submitter submitter; member
560 scmd->submitter != SUBMITTED_BY_SCSI_ERROR_HANDLER) in scsi_check_sense()1121 scmd->submitter = SUBMITTED_BY_SCSI_ERROR_HANDLER; in scsi_send_eh_cmnd()2415 scmd->submitter = SUBMITTED_BY_SCSI_RESET_IOCTL; in scsi_ioctl_reset()
1553 cmd->submitter = 0; in scsi_prepare_cmd()1611 switch (cmd->submitter) { in scsi_done_internal()1754 cmd->submitter = SUBMITTED_BY_BLOCK_LAYER; in scsi_queue_rq()
156 the patch (unless the submitter is the maintainer of the area) and CC: to
523 have been communicated back to the submitter. I am satisfied524 with the submitter's response to my comments.
796 The tip maintainers and submaintainers try to reply to the submitter
56 command was accepted by hardware. This allows the submitter to know if the
337 - submitter has given up waiting for it
423 initialized in order for the submitter to be notified that a
100 changed to 'Accepted' and the submitter will be notified by mail. This
Completed in 31 milliseconds