Searched refs:abandon (Results 1 – 11 of 11) sorted by relevance
96 goto abandon; in netfs_retry_read_subrequests()139 goto abandon; in netfs_retry_read_subrequests()215 goto abandon; in netfs_retry_read_subrequests()243 abandon: in netfs_retry_read_subrequests()
224 goto abandon; in __fscache_write_to_cache()230 goto abandon; in __fscache_write_to_cache()261 abandon: in __fscache_write_to_cache()
778 goto abandon; in iptfs_reassem_cont()785 goto abandon; in iptfs_reassem_cont()807 goto abandon; in iptfs_reassem_cont()815 goto abandon; in iptfs_reassem_cont()826 goto abandon; in iptfs_reassem_cont()836 goto abandon; in iptfs_reassem_cont()857 goto abandon; in iptfs_reassem_cont()866 goto abandon; in iptfs_reassem_cont()874 goto abandon; in iptfs_reassem_cont()909 goto abandon; in iptfs_reassem_cont()[all …]
224 Note that it is perfectly legal to "abandon" a request object:
100 commit. In that case, abandon the attempt. Do the same, if Git fails to revert
143 perhaps more robust. Just don't hesitate to abandon the idea if it looks like
252 prevent state 5 then we must abandon our "nice property" and check whether a
3247 goto abandon; in console_flush_all()3257 abandon: in console_flush_all()
600 herd7 knows to abandon an execution as soon as the "filter" expression611 value? Wouldn't that cause herd7 to abandon the execution prematurely
1118 restart or abandon R'.
1221 it to abandon processing before it was complete. Some CCBs may have been