@gschorcht’s code tends to be very good usually, so I think you don’t have to do much. It’s unfortunate that it didn’t receive a review earlier and these days he doesn’t have much time to spare for RIOT.
So to revive this you would have to
- rebase the branch onto the current master, fix the merge conflicts (e.g. auto_init moved to
drivers/saul/init_devs/init.c) - address @maribu’s review comments (ideally as separate commits, you can squash them later)
Then create a new PR with your branch, we’ll try to review it sooner this time 