On Thu, 2017-05-04 at 15:50 -0700, Bart Van Assche wrote:
> Hello Nic,
>
> This series consists of several patches that I had posted before and
> that have been rebased and retested on top of your for-next branch and
> also of several new patches. Sorry that I had not yet posted these
> patches earlier - I was busy with block layer and SCSI core fixes.
> Please have a look at these patches.
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.
This is important because:
- To know which bug-fixes are for existing code, instead of bug-fixes
that are a consequence of other changes.
- To know bug-fixes for existing code have been tested + verified
separate from any other changes.
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.
Doing a quick scan, I see the same thing happening in this series.
So please send me only the bug-fixes for existing code to review as
v4.12-rc items, and put else in a separate series for v4.13-rc1.
--
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
