Steffen, > Martin, is it possible that you re-wrote your for-next and it now no > longer contains a merged 5.4/scsi-postmerge with those fixes? At > least I cannot find the fix code in next-20190917 and it fails again > for me. Yes, looks like you're right. Not sure how I managed to mess that up. I must have inadvertently done a reset in the wrong worktree because my for-next branch maintenance script only does merges. In any case, since Linus has pulled the block tree dependencies, I'll rebase the postmerge branch on top of current linus/master and create a new for-next. Thanks for the heads-up! -- Martin K. Petersen Oracle Linux Engineering
