Message ID | 1675254998-4951-1-git-send-email-yangtiezhu@loongson.cn (mailing list archive) |
---|---|
Headers | show |
Series | bpf: Replace BPF_ALU and BPF_JMP with BPF_ALU32 and BPF_JMP64 | expand |
On Wed, Feb 1, 2023 at 4:36 AM Tiezhu Yang <yangtiezhu@loongson.cn> wrote: > > The intention of this patchset is to make the code more readable, > no functional changes, based on bpf-next. > > If this patchset makes no sense, please ignore it and sorry for that. ... > 157 files changed, 4299 insertions(+), 4295 deletions(-) Are you trying to get to the top of lwn's "most active developers by lines changed" ? I'm sure you knew that it's most likely going to be rejected, yet you still sent it. why? Your developer's reputation suffers. Think quality and not quantity.
On 02/02/2023 07:26 PM, Alexei Starovoitov wrote: > On Wed, Feb 1, 2023 at 4:36 AM Tiezhu Yang <yangtiezhu@loongson.cn> wrote: >> >> The intention of this patchset is to make the code more readable, >> no functional changes, based on bpf-next. >> >> If this patchset makes no sense, please ignore it and sorry for that. > ... >> 157 files changed, 4299 insertions(+), 4295 deletions(-) > > Are you trying to get to the top of lwn's "most active developers by > lines changed" ? Oh, no, no intention of doing so. > I'm sure you knew that it's most likely going to be rejected, > yet you still sent it. why? Sorry for the trouble. Maybe just send patch #1 and #4 as RFC is a proper way. > Your developer's reputation suffers. > Think quality and not quantity. > Anyway, thank you for your reply.