[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c6f23ba9-b92f-a518-25ec-44f5f188b840@microchip.com>
Date: Fri, 30 Sep 2022 07:39:21 +0000
From: <Conor.Dooley@...rochip.com>
To: <lukas.bulwahn@...il.com>, <chenhuacai@...nel.org>
CC: <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 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?
Powered by blists - more mailing lists