Searched refs:submitter (Results 1 – 16 of 16) sorted by relevance
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
22 io-submitter.o \
141 struct io_submitter *submitter = vio->completion.vdo->io_submitter; in get_bio_list() local142 struct bio_queue_data *bio_queue_data = &(submitter->bio_queue_data[vio->bio_zone]); in get_bio_list()
98 enum scsi_cmnd_submitter submitter; member
17 run by the submitter - but do put some thought into what you're changing and
575 scmd->submitter != SUBMITTED_BY_SCSI_ERROR_HANDLER) in scsi_check_sense()1175 scmd->submitter = SUBMITTED_BY_SCSI_ERROR_HANDLER; in scsi_send_eh_cmnd()2486 scmd->submitter = SUBMITTED_BY_SCSI_RESET_IOCTL; in scsi_ioctl_reset()
1665 cmd->submitter = 0; in scsi_prepare_cmd()1716 switch (cmd->submitter) { in scsi_done_internal()1866 cmd->submitter = SUBMITTED_BY_BLOCK_LAYER; in scsi_queue_rq()
185 the patch (unless the submitter is the maintainer of the area) and CC: to
569 have been communicated back to the submitter. I am satisfied570 with the submitter's response to my comments.
845 The tip maintainers and submaintainers try to reply to the submitter
353 submitter is using bad CR address on purpose.
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