From: Tiezhu Yang <yangtiezhu@loongson.cn>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>, bpf <bpf@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH bpf-next 0/4] bpf: Replace BPF_ALU and BPF_JMP with BPF_ALU32 and BPF_JMP64
Date: Thu, 2 Feb 2023 20:55:47 +0800 [thread overview]
Message-ID: <ba068c07-1337-3efc-ce4d-045d77dffd50@loongson.cn> (raw)
In-Reply-To: <CAADnVQKWWf6==B=X+2zazt1dmfK6ENAaGWWS_2QkX4bDJrJJNg@mail.gmail.com>
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.
prev parent reply other threads:[~2023-02-02 12:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 12:36 Tiezhu Yang
2023-02-01 12:36 ` [PATCH bpf-next 1/4] bpf: Add new macro " Tiezhu Yang
2023-02-01 14:59 ` Dave Thaler
2023-02-01 12:36 ` [PATCH bpf-next 2/4] bpf: treewide: Clean up BPF_ALU and BPF_JMP Tiezhu Yang
2023-02-02 4:01 ` kernel test robot
2023-02-01 12:36 ` [PATCH bpf-next 3/4] bpf: treewide: Clean up BPF_ALU_* and BPF_JMP_* Tiezhu Yang
2023-02-01 12:36 ` [PATCH bpf-next 4/4] bpf: Mark BPF_ALU and BPF_JMP as deprecated Tiezhu Yang
2023-02-02 11:26 ` [PATCH bpf-next 0/4] bpf: Replace BPF_ALU and BPF_JMP with BPF_ALU32 and BPF_JMP64 Alexei Starovoitov
2023-02-02 12:55 ` Tiezhu Yang [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ba068c07-1337-3efc-ce4d-045d77dffd50@loongson.cn \
--to=yangtiezhu@loongson.cn \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®