> > Now I'm confused, isn't this the same patch I picked this morning from > you and is already applied in chrome-platform for-next? >
Sorry, I didn't see that it was already applied in for-next. Just ignore this patch and assume that the next two in this series are based off the current state of for-next.
