Searched refs:submitter (Results 1 – 10 of 10) 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()194 static int prep_more_ios(struct submitter *s, unsigned max_ios) in prep_more_ios()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()[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
148 the patch (unless the submitter is the maintainer of the area) and CC: to
72 It's best if the submitter and copyright owner
520 have been communicated back to the submitter. I am satisfied521 with the submitter's response to my comments.
56 command was accepted by hardware. This allows the submitter to know if the
337 - submitter has given up waiting for it
404 initialized in order for the submitter to be notified that a
73 changed to 'Accepted' and the submitter will be notified by mail. This
