linux-kernel - Re: [PATCH] loongarch: update config files

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: <CAAhV-H4ivkPPU2eQBSv1M8q0gT6M3X0po_9-yYGML7WfCVYBZg@mail.gmail.com>
Date:   Fri, 30 Sep 2022 16:03:32 +0800
From:   Huacai Chen <chenhuacai@...nel.org>
To:     Conor.Dooley@...rochip.com
Cc:     lukas.bulwahn@...il.com, kernel-janitors@...r.kernel.org,
        linux-kernel@...r.kernel.org, kernel@...0n.name,
        loongarch@...ts.linux.dev
Subject: Re: [PATCH] loongarch: update config files

On Fri, Sep 30, 2022 at 3:39 PM <Conor.Dooley@...rochip.com> wrote:
>
> On 30/09/2022 08:22, Lukas Bulwahn wrote:
> > EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> >
> > On Fri, Sep 30, 2022 at 4:46 AM Huacai Chen <chenhuacai@...nel.org> wrote:
> >>
> >> On Thu, Sep 29, 2022 at 6:44 PM Lukas Bulwahn <lukas.bulwahn@...il.com> wrote:
> >>>
> >>> On Thu, Sep 29, 2022 at 12:42 PM Huacai Chen <chenhuacai@...nel.org> wrote:
> >>>>
> >>>> Hi, Lukas,
> >>>>
> >>>> Thank you for your patch, it is queued for loongarch-next, and may be
> >>>> squashed to another patch with your S-o-B if you have no objections.
> >>>>
> >>>> Huacai
> >>>>
> >>>
> >>> Feel free to squash as you see fit. I cannot recall sending something
> >>> specific for loongarch-next, though.
> >> Emmm, my meaning is squash your patch to mine and keep a S-o-B in that
> >> patch [1]. :)
> >>
> >> [1] https://git.kernel.org/pub/scm/linux/kernel/git/chenhuacai/linux-loongson.git/commit/?h=loongarch-next
> >>
> >
> > Process-wise that seems a bit strange (i.e., just mixing S-o-B by
> > multiple people, how do you bisect which individual change broke
> > something [you would need a second manual step of investigation],
> > etc.), but sure go ahead.
>
> Looks like each of yourself, Youling and Tiezhu should also have
> Co-developed-by tags, no?
Yes, that is needed.

Huacai
>