Hi Xiubo & Co, On Mon, 2017-03-27 at 17:07 +0800, lixiubo@xxxxxxxxxxxxxxxxxxxx wrote: > From: Xiubo Li <lixiubo@xxxxxxxxxxxxxxxxxxxx> > > Changed for V5: > - This only includes #1 and #2. And for old #3, #4 are still reviewing. > - #1, since the issue reported by Ilias is a separate new one, and will > create a new patch later. > - #2, address the issue pointed out by Mike, thanks. > - #1 and #2 have been tested by Ilias in BIDI case, thanks. > > Changed for V4: > - re-order the #3, #4 at the head. > - merge most of the #5 to others. > > Xiubo Li (2): > tcmu: Fix possible overwrite of t_data_sg's last iov[] > tcmu: Fix wrongly calculating of the base_command_size > > drivers/target/target_core_user.c | 44 +++++++++++++++++++++++++++------------ > 1 file changed, 31 insertions(+), 13 deletions(-) > Applied to target-pending/master, along with CC's for 3.19.y stable. Thanks Xiubo ! Btw, I fixed-up the ordering of the Reviewed-by + Tested-by + Signed-off-by tags on the patches here: https://git.kernel.org/pub/scm/linux/kernel/git/nab/target-pending.git/commit/?id=ab22d2604c86ceb01bb2725c9860b88a7dd383bb https://git.kernel.org/pub/scm/linux/kernel/git/nab/target-pending.git/commit/?id=abe342a5b4b5aa579f6bf40ba73447c699e6b579 Just for future reference, the flow of these tags should reflect the history of the patch. Eg: Reviewed-by: First reviewer <foo@xxxxxxx> Tested-by: First tester <foo2@xxxxxxxx> Reviewed-by: Second reviewer <foo3@xxxxxxxx> Signed-off-by: Patch Author <you@xxxxxxxxxxxxxx> and then once the subsystem maintainer merges it into his tree, they add their own: Signed-off-by: Subsystem Maintainer <superturboarray@xxxxxxxxxxxxxxxx> Beyond that, what is the status of the other two feature improvement patches..? Do you intend to post those (again) as v4.12-rc1 material..?
