From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Huacai Chen <chenhuacai@kernel.org>
Cc: Conor Dooley <conor@kernel.org>,
Binbin Zhou <zhoubb.aaron@gmail.com>,
Binbin Zhou <zhoubinbin@loongson.cn>,
Huacai Chen <chenhuacai@loongson.cn>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, Xuerui Wang <kernel@xen0n.name>,
loongarch@lists.linux.dev, Jiaxun Yang <jiaxun.yang@flygoat.com>,
Hongliang Wang <wanghongliang@loongson.cn>
Subject: Re: [PATCH v6 0/7] LoongArch: Add built-in dtb support
Date: Tue, 9 Jan 2024 14:33:37 +0100 [thread overview]
Message-ID: <194f95be-59f2-4c71-8642-80e5ced9bf6b@linaro.org> (raw)
In-Reply-To: <CAAhV-H7QQD9ida52rvkhUgzU6O1KmKD7EsNxn=7YyVZP4HXa=Q@mail.gmail.com>
On 09/01/2024 13:13, Huacai Chen wrote:
> Hi, Krzysztof,
>
> On Tue, Jan 9, 2024 at 7:14 PM Krzysztof Kozlowski
> <krzysztof.kozlowski@linaro.org> wrote:
>>
>> On 09/01/2024 10:57, Huacai Chen wrote:
>>> Applied to loongarch-next, thanks.
>>>
>>
>> It's merge window, why do you apply patches? For which cycle?
> I'm sorry I forgot to reply to the email when I applied patches, the
> patches have already been pulled in linux-next some days before.
Really? I cannot find them on next-20240108, so what happened?
Are you aware that patches should be in next for "few next cycles"
minimum (which means few days or even a week)?
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-01-09 13:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-22 8:00 [PATCH v6 0/7] LoongArch: Add built-in dtb support Binbin Zhou
2023-12-22 8:00 ` [PATCH v6 1/7] dt-bindings: loongarch: Add CPU bindings for LoongArch Binbin Zhou
2023-12-22 8:00 ` [PATCH v6 2/7] dt-bindings: loongarch: Add Loongson SoC boards compatibles Binbin Zhou
2023-12-22 8:00 ` [PATCH v6 3/7] LoongArch: Allow device trees to be built into the kernel Binbin Zhou
2023-12-22 8:01 ` [PATCH v6 4/7] LoongArch: dts: DeviceTree for Loongson-2K0500 Binbin Zhou
2023-12-22 8:01 ` [PATCH v6 5/7] LoongArch: dts: DeviceTree for Loongson-2K1000 Binbin Zhou
2023-12-22 8:01 ` [PATCH v6 6/7] LoongArch: dts: DeviceTree for Loongson-2K2000 Binbin Zhou
2023-12-22 8:01 ` [PATCH v6 7/7] LoongArch: Parsing CPU-related information from DTS Binbin Zhou
2023-12-22 15:38 ` [PATCH v6 0/7] LoongArch: Add built-in dtb support Conor Dooley
2023-12-27 6:04 ` Binbin Zhou
2023-12-28 14:09 ` Conor Dooley
2023-12-29 15:10 ` Huacai Chen
2024-01-09 9:57 ` Huacai Chen
2024-01-09 11:14 ` Krzysztof Kozlowski
2024-01-09 12:13 ` Huacai Chen
2024-01-09 13:33 ` Krzysztof Kozlowski [this message]
2024-01-09 15:02 ` Huacai Chen
2024-01-09 15:13 ` Krzysztof Kozlowski
2024-01-09 15:25 ` Huacai Chen
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=194f95be-59f2-4c71-8642-80e5ced9bf6b@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=chenhuacai@kernel.org \
--cc=chenhuacai@loongson.cn \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jiaxun.yang@flygoat.com \
--cc=kernel@xen0n.name \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=loongarch@lists.linux.dev \
--cc=robh+dt@kernel.org \
--cc=wanghongliang@loongson.cn \
--cc=zhoubb.aaron@gmail.com \
--cc=zhoubinbin@loongson.cn \
/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