From: <Conor.Dooley@microchip.com>
To: <lukas.bulwahn@gmail.com>, <chenhuacai@kernel.org>
Cc: <kernel-janitors@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<kernel@xen0n.name>, <loongarch@lists.linux.dev>
Subject: Re: [PATCH] loongarch: update config files
Date: Fri, 30 Sep 2022 07:39:21 +0000 [thread overview]
Message-ID: <c6f23ba9-b92f-a518-25ec-44f5f188b840@microchip.com> (raw)
In-Reply-To: <CAKXUXMw731xNrqUzrCE1jRd25vfWdYFf-donLosOYOTqcm9JiQ@mail.gmail.com>
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@kernel.org> wrote:
>>
>> On Thu, Sep 29, 2022 at 6:44 PM Lukas Bulwahn <lukas.bulwahn@gmail.com> wrote:
>>>
>>> On Thu, Sep 29, 2022 at 12:42 PM Huacai Chen <chenhuacai@kernel.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?
next prev parent reply other threads:[~2022-09-30 7:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 10:14 Lukas Bulwahn
2022-09-29 10:41 ` Huacai Chen
2022-09-29 10:44 ` Lukas Bulwahn
2022-09-30 2:46 ` Huacai Chen
2022-09-30 7:22 ` Lukas Bulwahn
2022-09-30 7:39 ` Conor.Dooley [this message]
2022-09-30 8:03 ` Huacai Chen
2022-09-30 10:09 ` WANG Xuerui
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c6f23ba9-b92f-a518-25ec-44f5f188b840@microchip.com \
--to=conor.dooley@microchip.com \
--cc=chenhuacai@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=kernel@xen0n.name \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=lukas.bulwahn@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®