linux-kernel - Re: [PATCH v8 0/2] Kbuild: DWARF v5 support

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: <CA+icZUVFrk4L+CUo+o3pdsOjaJPKCqnP0zmTuaOoYLg4wyHkbw@mail.gmail.com>
Date:   Thu, 4 Feb 2021 09:22:58 +0100
From:   Sedat Dilek <sedat.dilek@...il.com>
To:     Nick Desaulniers <ndesaulniers@...gle.com>
Cc:     Masahiro Yamada <masahiroy@...nel.org>,
        Nathan Chancellor <natechancellor@...il.com>,
        Andrew Morton <akpm@...ux-foundation.org>,
        LKML <linux-kernel@...r.kernel.org>,
        Clang-Built-Linux ML <clang-built-linux@...glegroups.com>,
        Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
        linux-arch <linux-arch@...r.kernel.org>,
        Jakub Jelinek <jakub@...hat.com>,
        Fangrui Song <maskray@...gle.com>,
        Caroline Tice <cmtice@...gle.com>,
        Nick Clifton <nickc@...hat.com>, Yonghong Song <yhs@...com>,
        Jiri Olsa <jolsa@...nel.org>,
        Andrii Nakryiko <andrii@...nel.org>,
        Arnaldo Carvalho de Melo <acme@...nel.org>,
        Arvind Sankar <nivedita@...m.mit.edu>,
        Chris Murphy <bugzilla@...orremedies.com>
Subject: Re: [PATCH v8 0/2] Kbuild: DWARF v5 support

On Thu, Feb 4, 2021 at 8:45 AM Nick Desaulniers <ndesaulniers@...gle.com> wrote:
>
> On Wed, Feb 3, 2021 at 10:58 PM Sedat Dilek <sedat.dilek@...il.com> wrote:
> >
> > I guess I need to test harder to get a Tested-by credit :-)?
>
> You're right Sedat, I'm sorry.  Your testing is invaluable; thank you
> for taking the time to help and credit is a powerful incentive.
>
> It can be difficult to know whether to carry forward tags or not when
> a patch is revised.
>
> Keeping track whether someone sent an explicit Tested By vs including
> it based on feedback that implied they tried it.  If you've tested v7
> or v8, please reply explicitly with tested by tags, or perhaps
> Masahiro can apply those for you.
>

Unfortunately, some recent patches around CBL and kbuild miss my
Tested-by's and are already queued up in the remote Git's.
Maybe, I was simply pissed off this fact when writing my response to you.

Feel free to add my...

   Tested-by: Sedat Dilek <sedat.dilek@...il.com> # v1-v8 with
LLVM/Clang v11.0.1+ & v12.0.0-rc1 amd64

Looking at the (git) diff v7 -> v8 - seen from the code - nothing changed.

Feel free to add the links to thread(s) and patch(es) I gave as a
feedback in my other response.

One reason for missed Tested-by's I see is I am NOT subscribed to some
mailing-list.

> It can be difficult to know what's broken if you apply too many out of
> tree patches though.
>

"Nicht verkomplifizieren."
In English: "R(e)D(u)C(e) complexity" is normally one of my life philosophies.

Fighting with... "As usual: It has to work in my development
environment - first."

Sorry, I insisted that it *has* to work in my environment.
It has no secrets - all patches I have queued up in my custom patchset
is publically available.
That does not mean all of them are or will be upstreamed.

Bonne chance with the Linux-BPF folks and send my apologies to have fooled them.
It's one of my """strength of character""" (note 3 quotes) :-).

- Sedat -