On Fri, 2017-05-05 at 03:36 +0000, Bart Van Assche wrote: > On Thu, 2017-05-04 at 20:32 -0700, Nicholas A. Bellinger wrote: > > This series is intermixing random improvements and bug-fixes during the > > middle of a merge window, and I've asked multiple times now that > > bug-fixes for existing mainline code must always precede anything else. > > The fixes can be cherry-picked if you want. But if you prefer so, I will > repost this series with the bug fixes first. You've been asked numerous times to put bug-fixes first, but yet these types of series continue to show up. > > For the former, every series I've gotten from you in the last six months > > has had at least one patch that is a bug-fix for some issue the series > > itself introduced, and it's never been obvious. > > That's wrong. I never do that if I post a patch series. > > > Doing a quick scan, I see the same thing happening in this series. > > Please look again. That's not the case with this patch series. > I have, and this series is no different. Anyways, I'll comment inline and pick-up the few fixes that are valid. -- To unsubscribe from this list: send the line "unsubscribe target-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
