[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f6357d19-9bd9-e9f4-6e9d-97a73f61560d@linux.dev>
Date: Wed, 25 Oct 2023 09:54:27 -0700
From: Martin KaFai Lau <martin.lau@...ux.dev>
To: Jiri Pirko <jiri@...nulli.us>
Cc: Daniel Borkmann <daniel@...earbox.net>, bpf@...r.kernel.org,
netdev@...r.kernel.org, razor@...ckwall.org, ast@...nel.org,
andrii@...nel.org, john.fastabend@...il.com, sdf@...gle.com,
toke@...nel.org, kuba@...nel.org, andrew@...n.ch
Subject: Re: [PATCH bpf-next v4 0/7] Add bpf programmable net device
On 10/25/23 8:50 AM, Jiri Pirko wrote:
> Wed, Oct 25, 2023 at 01:50:25AM CEST, patchwork-bot+netdevbpf@...nel.org wrote:
>> Hello:
>>
>> This series was applied to bpf/bpf-next.git (master)
>> by Martin KaFai Lau <martin.lau@...nel.org>:
>
> Interesting, applied within 2 hours after send. You bpf people don't
> care about some 24h timeout?
24hr? The v1 was posted to both netdev and bpf list on 9/25. It was 10/24
yesterday. The part you commented in patch 1 had not been changed much since v1,
so there was a month of time. netdev is always on the cc list. Multiple people
(Andrew, Jakub...etc) had already helped to review and Daniel had addressed the
comments. The change history had been diminishing from v1 to v4 and v4 changes
was mostly nit-picking already.
Powered by blists - more mailing lists