How are hardware specific bugs and features tested in the Linux kernel? -

how kernel developers test changes on specific hardware? if don't have particular type of hardware, how figure out issue happening?

generally, kernel developers responsible writing drivers specific piece of hardware happens tester , owns piece of hardware.

if developer comes across bug (or if people report bug) on piece of hardware, 1 fixes it. it'd silly ask fix or maintain driver hardware not own.

as higher level kernel features, here linux development paradigm comes play. linux employs merge window strategy releasing since it's unrealistic ask every developer test changes on every single possible combination of hardware , software combinations.

instead, after major release, merge window opened around 2 weeks developers can push in significant changes, new drivers , features. after merge window closes, no more patches new changes accepted.

during time merge window closed, developers have chance test newly merged code on own hardware , report bugs , breakages. usually, developer works person introduced change fix bug. developer can send fix included in next release candidate.

a new release candidate released weekly. when linus happy of bugs introduced version has been fixed, makes major release , cycle starts again.

in other words, answer question don't. no 1 developer responsible nor expected fix problems other people. developer responsible part of kernel maintains.