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] [day] [month] [year] [list]
Message-ID: <CAEf4Bzb4CQTbxXQXnukVfV5T5dWDutvyL6n7Krfw+T0Gc_aGSA@mail.gmail.com>
Date:   Tue, 1 Dec 2020 17:30:37 -0800
From:   Andrii Nakryiko <andrii.nakryiko@...il.com>
To:     Prankur gupta <prankgup@...com>
Cc:     Alexei Starovoitov <alexei.starovoitov@...il.com>,
        bpf <bpf@...r.kernel.org>, Kernel Team <kernel-team@...com>,
        Networking <netdev@...r.kernel.org>
Subject: Re: [PATCH bpf-next 0/2] Add support to set window_clamp from bpf setsockops

On Tue, Dec 1, 2020 at 12:24 PM Prankur gupta <prankgup@...com> wrote:
>
> From: Prankur Gupta <prankgup@...com>
>
> No reason in particular.
> Updated the code (patch v2) to have logic as tcp setsockopt for tCP_WINDOW_CLAMP.
>
> PS: First time trying git send-em,ail, pleas elet me know if this is not the right way to reply.

I use send-email for sending patches only, I reply from Gmail or
Thunderbird (from work account). The latter has a plain text mode,
while Outlook doesn't.

But also, you need to add v2 to each patch, not just cover letter. You
can do that when using `git format-patch --subject-prefix='PATCH v2
bpf-next' ...`.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ