On Sat, 2018-01-27 at 19:23 -0500, Mike Snitzer wrote: > Your contributions do _not_ make up for your inability to work well with > others. Tiresome doesn't begin to describe these interactions. > > Life is too short to continue enduring your bullshit. > > But do let us know when you have something of substance to contribute > (hint: code talks). Sorry Mike but what you wrote above is not only very gross but it is also wrong. What I did in my e-mail is to identify technical problems in Ming's work. Additionally, it seems like you forgot that recently I helped Ming? My patch "blk-mq: Avoid that blk_mq_delay_run_hw_queue() introduces unintended delays" has been queued by Jens for kernel v4.16 and solves a problem that Ming has been working on for two months but that he was unable to come up with a proper fix for. Additionally, there is something that you have to explain: the patch "dm mpath: don't call blk_mq_delay_run_hw_queue() in case of BLK_STS_RESOURCE" that you have queued in your tree is wrong and introduces a regression (https://git.kernel.org/pub/scm/linux/kernel/git/snitzer/linux.git/commit/?h=dm-4.16&id=316a795ad388e0c3ca613454851a28079d917a92). I'm surprised that you have not yet reverted that patch? BTW, in case you would not yet have noticed my patch "blk-mq: Avoid that blk_mq_delay_run_hw_queue() introduces unintended delays" eliminates the delay you referred to in the description of that patch. In case the above would not yet have addressed the technical issue(s) you are facing, I would really appreciate it if you would stop using insults and if you could explain what technical problems you are facing. Isn't that what the Linux kernel is about, namely about collaboration between technical people from different organizations? Isn't that what made the Linux kernel great? Bart. -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
