On Tue, Mar 5, 2019 at 10:55 AM Finn Thain <fthain@xxxxxxxxxxxxxxxxxxx> wrote:
That leaves bvme6000, hp300, mvme147 and mvme16x. Those have not been tested. Here are some options for those platforms: 1) Apply the patches untested (gaining new clocksources and some API modernization for m68k, while fixing old bugs and potentially introducing new bugs).
This is what I usually do with ARM machines when I don't get any tests or reviews after a reasonable time lap, > month for sure is a reasonable time for users to have all opportunity in the world to test patches. If things break, users will report it as is custom and the author will be expected to work with them to fix them then, we do this all the time. Those users who want everything tested before it gets merged should provide resources or time for testing. Just my €0.01 Linus Walleij
