Tags

mtp-testing before 01-28 update

Before msm-next rebase on 12/12

12/04 mtp testing

- Several related to incorrect error checking/handling (Various)
- Prevent IRQ storm on MDP5 HDMI hotplug (Todor)
- Don't capture crash state if unsupported (Sharat)
- Properly grab vblank reference in atomic wait for commit done (Sean)

Cc: Sharat Masetty <smasetty@codeaurora.org>
Cc: Todor Tomov <todor.tomov@linaro.org>
Cc: Sean Paul <seanpaul@chromium.org>

tag

- Several related to incorrect error checking/handling (Various)
- Prevent IRQ storm on MDP5 HDMI hotplug (Todor)
- Don't capture crash state if unsupported (Sharat)
- Properly grab vblank reference in atomic wait for commit done (Sean)

Cc: Sharat Masetty <smasetty@codeaurora.org>
Cc: Todor Tomov <todor.tomov@linaro.org>
Cc: Sean Paul <seanpaul@chromium.org>

mtp-testing before the 11/16 force-push

tag

Same as msm_forklift_sandbox_boots, but it boots

cheza sandbox on top of msm-next on top of cros/chromeos-4.19

for-next tag before msm-next 4.20 rebase

Fixed conflicts and build errors in interconnect patches.

Tag before pushing the 10/03 sandbox

Tagging mtp-testing on top of 0904 sandbox

mtp-testing as of 8/22, before 8/23 force push

Tag with regulator toggling

MTP Testing from 7/26, formerly the mtp-testing-0723 branch

for-next with the unsquashed modifier removal patch on top

<<<<<  NOT BISECTABLE >>>>>

for-next v3 with a few fixups on the top that were needed to make it run
on cheza.