lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0b927a07-6fbb-0e5b-e791-9558c9ea8e63@molgen.mpg.de>
Date:   Tue, 8 Sep 2020 13:20:15 +0200
From:   Paul Menzel <pmenzel@...gen.mpg.de>
To:     Björn Töpel <bjorn.topel@...el.com>,
        Björn Töpel <bjorn.topel@...il.com>,
        ast@...nel.org, daniel@...earbox.net, netdev@...r.kernel.org,
        bpf@...r.kernel.org
Cc:     kuba@...nel.org, intel-wired-lan@...ts.osuosl.org,
        magnus.karlsson@...el.com
Subject: Re: [Intel-wired-lan] [PATCH bpf-next 4/4] ixgbe, xsk: use
 XSK_NAPI_WEIGHT as NAPI poll budget

Dear Björn,


Am 08.09.20 um 13:12 schrieb Björn Töpel:
> On 2020-09-08 12:12, Paul Menzel wrote:

>> Am 07.09.20 um 17:02 schrieb Björn Töpel:
>>> From: Björn Töpel <bjorn.topel@...el.com>
>>>
>>> Start using XSK_NAPI_WEIGHT as NAPI poll budget for the AF_XDP Rx
>>> zero-copy path.
>>
>> Could you please add the description from the patch series cover 
>> letter to this commit too? To my knowledge, the message in the cover 
>> letter won’t be stored in the git repository.
> 
> Paul, thanks for the input! The netdev/bpf trees always include the 
> cover letter in the merge commit.

Yes, for pull/merge requests. But you posted them to the list, so I’d 
assume they will be applied with `git am` and not merged, or am I 
missing something. Could you please point me to a merge commit where the 
patches were posted to the list?


Kind regards,

Paul

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ