I've removed it in D56136.
I can remove it here too if you want.
Thanks

RFC2462 -> RFC 4862.

I'd recommend split that into a different review. It is not part of Change prelist_update() return type to void, but a good commit log is useful for users those use git blame to find out why this line was changed.

Generally, for a commit, do one thing if possible.

New code should use uint32_t. I would keep existing code as is, given it is not part of the change lines related to Change prelist_update() return type to void, and also only change one u_int32_t -> uint32_t does not serve much value.

I have ever had a plan to change them all, but there're too many usage.

% grep -Er 'u_int(8|16|32)_t' sys | wc -l
   51240

I abort finally, such a big change ( u_int(8|16|32)_t -> uint(8|16|32)_t ) will makes troubles when doing MFC.

I verified this function conforms to the new RFC.
However, IMHO a commit that only updates a single comment line is not useful.
I'll explain it in the commit message body instead to be searchable.

I'll eventually relocate many parts of this function to new one and fix their types along the way.
This will be the only old type left.
That's why I updated it here.

I have ever had a plan to change them all, but there're too many usage.

Yes, better to remove them incrementally when making other nearby changes, like we've done with e.g., boolean_t. u_int*_t does not hurt anyone, it is not worth the churn to remove it all at once.

That's fine.