Elliott Mitchell

There seems to be disagreement on the interpretation of "draft" here. I was choosing "draft" to indicate that while this is not 100% ready, but it is _mostly_ ready and...

The second and third are surprisingly effective at pushing merging further. There are a large number of spots which don't really care _which_ interrupt structure they use, they simply need...

Hopefully this is a bit more obvious. "a_bikeshed_string_for_sed_to_target" is simply a handy string for `sed` to target, not an actual suggestion. Theory is this collects all the information together for...

Appears the issue started at 7fed2e3a32d6b44adca73179b98730d1938c7767. Even for consensus on a trivial issue that is impressive.

I really was kind of hoping for activity on this. The first two can readily be done before trying to review the later commits (GitHub might automatically close the pull...

I'll confess this is mostly meant to suggest there really is another interface being hidden here. Mainly `intr_add_handler()` and `intr_describe()` very definitely point to a border. Some drivers would benefit...

Gah! Keep trying to draw a borderline and some bits are quite unclear.

This is an alternative. I'm pretty sure I've got `intr_describe_irq()` split correctly. Problem is I'm rather less confident of how `intr_isrc_assign_cpu()` should be split. Then there are a bunch of...

I'm rather unsure where the border goes here. To tell the truth, right now I'm primarily interested in the two at the front. I'm trying to port a driver for...

I do not guarantee I've sufficiently resolved issues brought up via Phabricator, even though I have tried. This seems the way to go.