Skip to contentSkip to conversation

The linux-rdma staging branches

DISCUSSION Steve Wise 1 participant 2 messages Aug 1, 2017 – Aug 17, 2017 InfiniBand

lore
Share & tools
lore

Steve Wise

author
#0 lore raw

He Doug, I want to get chelsio's QA tied into regular regression testing of fixes you have staged for release-next as well as RC fixes staged for the current RC release. Which branches do they want to track for regression testing?

Also, does anyone have "best practices" for how QA orgs should regression test linux kernels through the release process?

Thanks,

Steve.

--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html

author
#1 lore raw

ping.

So are k.o/for-next and k.o/for-X.Y-rc branche the ones to watch and test in your git.kernel.org tree? I'm trying to tie chelsio's QA into this, and any help is greatly appreciated!

Is there some process other vendors or interested parties care to share on trying to catch rdma regressions early? This whole recent breakage of the rdma core that made it into 4.9 and 4.12 is painful, to say the least.

Thanks!

Steve.

Quoted 9 lines

He Doug, I want to get chelsio's QA tied into regular regression testing of fixes you have staged for release-next as well as RC fixes staged for the current RC release. Which branches do they want to track for regression testing?

Also, does anyone have "best practices" for how QA orgs should regression test linux kernels through the release process?

Quoted 8 lines

Thanks,

Steve.

--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html

--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html