netdev - Re: [PATCH v3 bpf-next 02/18] bpf: Add bpf_arch_text

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]

Date:   Mon, 11 Nov 2019 09:14:03 +0100
From:   Peter Zijlstra <peterz@...radead.org>
To:     David Miller <davem@...emloft.net>
Cc:     alexei.starovoitov@...il.com, ast@...nel.org, daniel@...earbox.net,
        x86@...nel.org, netdev@...r.kernel.org, bpf@...r.kernel.org,
        Kernel-team@...com
Subject: Re: [PATCH v3 bpf-next 02/18] bpf: Add bpf_arch_text_poke() helper

On Fri, Nov 08, 2019 at 01:39:24PM -0800, David Miller wrote:
> From: Peter Zijlstra <peterz@...radead.org>
> Date: Fri, 8 Nov 2019 22:36:24 +0100
> 
> > The cover leter is not preserved and should therefore
>  ...
> 
> The cover letter is +ALWAYS+ preserved, we put them in the merge
> commit.

Good to know; is this a netdev special? I've not seen this before.

Is there a convenient git command to find the merge commit for a given
regular commit? Say I've used git-blame to find a troublesome commit,
then how do I find the merge commit for it?

Also, I still think this does not excuse weak individual Changelogs.