The headers look good and Murdock will soon confirm that all the tests are running ;)

But does it make sense to merge this before there is any code that makes use of this?

But does it make sense to merge this before there is any code that makes use of this?

Will be coming in in the coming weeks. It would greatly reduce some rebasing hassle if it were merged (same goes for #12220 ;-))

I understand the reasoning that keeping PRs small would speed up the review process.
But I think interdependent PRs slow things down even more.

I review PRs one commit after the other, so that's already reasonable chunks.

On one hand, many reviewers (myself included) seem to prefer smaller updates as larger PRs just feel overwhelming. On the other, I prefer to get my code published and reviewed fast, so kinks can be ironed out, while I'm still working on follow-ups (which to my understanding are seperate units so should be separate PRs)

Also, in this specific instance the feature is expected to be quite large (think IPv6 fragmentation + reassembly + a lot more extra) so I rather go small logically divided steps.

Added a check to generically check if the header is any of the two SFR headers.

Squashed.