I think that the CI is failing on i686-unknown-linux-gnu because it didn't find the header files. What should I do to fix that?

If these are more recent than our kernel versions in CI, you will need to update libc-test/build.rs to skip them with a FIXME. If you do this, just make sure libc-test passes locally without the skips (assuming you have a newer version locally).

@rustbot author

Reminder, once the PR becomes ready for a review, use @rustbot ready.

I don't know why the style check fails. It says to replace the = with : in the c_enum, but the macro cannot accept :

help: replace equals symbol with a colon
     |
4760 -         PROC_EVENT_EXIT = 0x80000000,
4760 +         PROC_EVENT_EXIT: 0x80000000,

@rustbot ready

I've added c_enum to the ignore list in .ci/style.sh because rustfmt cannot handle the case when values are specified. If you have a better solution, I will implement it instead

The CI failures appear to be unrelated to the changes I made

@tgross35 do you know when the next release is coming out?

Probably within a couple of weeks. Usually it's about once every 6 weeks, this cycle got kind of slowed down with backport conflicts and CI issues.