Re: [ping 2]: [PATCH v4 0/5] MI notification on trace started/stopped

[Pedro Alves <palves@redhat.com>]

I do my best to review as much as possible.  In fact, my main
projects keep getting delayed for months as I can't ever find enough time/energy
to focus on them.  Unfortunately it tends to happen that I end up needing to
spend a very significant amount of time and energy through the patches/proposals.
The past weeks were a set back, as as you know, 7.6 had issues that needed
addressing.  It'd be great if patches/designs and submissions come up perfect
from the get go, or that I was smarter and could review faster, but that's
unfortunately not frequently the case.  The bigger the patch/series, the more
likely it is that it needs iteration.  I know you have several series waiting to
get in.  Please be patient.  If you look at CS submissions as a whole, you'll
notice that I'm usually reviewing/iterating over at least one at a
given time.  It's just that bigger ones require more energy, so they
take more to get through.  Next up, as I said before, is the range stepping
series.  Please let me focus on it and get it to completion, and context
switch to the async notifications afterwards.

Thanks,
-- 
Pedro Alves