Committed my DRM interface 1.2 change. It ties the DRM down to a specific device, which will make making a lower-level DRM layer much more sane. I have more evil plans, such as not allowing the X Server to addmap/map FB or MMIO areas that don't correspond to the areas that the card advertises through PCI. This will work well with the standalone Mesa and kdrive desires that the DRM tell userland where the FB/MMIO are, rather than the other way around.
Got a bug report from my first DRM interface change, about running two servers on different VTs on a single card, with both trying to enable the DRI. The set/getunique system which I deprecated the "set" half of in the 1.1 interface acted as a sort of lock preventing a second server from (re-)initializing the DRM. The removed "set" attempt let the second X Server partially initialize the DRM before it failed. In the process the kernel would become confused about where the lock was. So, I made it not allow a second lock-containing SHM area to be added, which locks out the 2nd X Server before it messes things up.
Played around in the PR database a bit. Closed some kern and i386 PRs, mostly due to them being already fixed. Fun to see myself shoot up to #12 of the non-ports PR busters on the PR stats page.