{"push_id":585035038,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"5916d4cbd601c9fc8e430f29e482f38c5becd707","before":"2be64087ca87140ec28d25e5b59c23f6e9d516f6","commits":[{"sha":"5916d4cbd601c9fc8e430f29e482f38c5becd707","author":{"email":"c208d1ecece4e5ef2e4fb72f0546c69cdce89063@gmail.com","name":"faux123"},"message":"aio: add aio support for iov_iter arguments\n\nThis adds iocb cmds which specify that memory is held in iov_iter\nstructures.  This lets kernel callers specify memory that can be\nexpressed in an iov_iter, which includes pages in bio_vec arrays.\n\nOnly kernel callers can provide an iov_iter so it doesn't make a lot of\nsense to expose the IOCB_CMD values for this as part of the user space\nABI.\n\nBut kernel callers should also be able to perform the usual aio\noperations which suggests using the the existing operation namespace and\nsupport code.\n\nSigned-off-by: Dave Kleikamp <dave.kleikamp@oracle.com>\nCc: Zach Brown <zab@zabbo.net>\nmodified for Mako from LKML reference\n\nSigned-off-by: faux123 <reioux@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Hybridmax/Hybridmax_Kernel_I9505/commits/5916d4cbd601c9fc8e430f29e482f38c5becd707"}]}