On 3/4/20 4:50 PM, Alexei Starovoitov wrote:
On Wed, Mar 4, 2020 at 7:39 AM Daniel Borkmann <daniel@xxxxxxxxxxxxx> wrote:
I was about to push the series out, but agree that there may be a risk for #ifndefs
in the BPF C code. If we want to be on safe side, #define FOO FOO would be needed.
There is really no risk.
Let's not be paranoid about it and uglify bpf.h for no reason.
From what I've seen it seems so, yes. I've pushed the series now. Worst case we can
always add the define FOO FOO before it's exposed.
Thanks,
Daniel
