From: PeterYin <peteryin.openbmc@gmail.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
patrick@stwcx.xyz, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>, Joel Stanley <joel@jms.id.au>,
Andrew Jeffery <andrew@aj.id.au>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 0/2] Add Facebook Minerva Harma (AST2600) BMC
Date: Mon, 4 Dec 2023 16:46:41 +0800 [thread overview]
Message-ID: <3ff5dcd7-69a3-4098-92c6-ed1e8f0bd8f9@gmail.com> (raw)
In-Reply-To: <fddcbad4-5368-4c2a-ba87-f4c4326a8385@linaro.org>
Krzysztof Kozlowski 於 12/4/23 16:20 寫道:
> On 04/12/2023 09:10, Peter Yin wrote:
>> Summary:
>> Add linux device tree entry related to Minerva Harma
>> specific devices connected to BMC SoC.
>>
>> v4:https://lore.kernel.org/all/20231204054131.1845775-3-peter.yin@quantatw.com/
>> v3:https://lore.kernel.org/all/20231123050415.3441429-3-peteryin.openbmc@gmail.com/
>> v2:https://lore.kernel.org/all/cdbc75b9-3be1-4017-9bee-c8f161b6843c@linaro.org/
>> v1:https://lore.kernel.org/all/20231024082404.735843-3-peteryin.openbmc@gmail.com/
>>
>> Change log
>> v4 -> v5
>> - Rename document and file from minerva-harma to harma.
>
> You must explain that you dropped people's review for some reason.
>
> Best regards,
> Krzysztof
>
Due to changes in the project name and content, please assist in
reviewing it.
Thanks,
Peter.
next prev parent reply other threads:[~2023-12-04 8:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-04 8:10 [PATCH v5 0/2] Add Facebook Minerva Harma (AST2600) BMC Peter Yin
2023-12-04 8:10 ` [PATCH v5 1/2] dt-bindings: arm: aspeed: add Meta Harma board Peter Yin
2023-12-04 8:20 ` Krzysztof Kozlowski
2023-12-04 8:10 ` [PATCH v5 2/2] ARM: dts: aspeed: Harma: Add Facebook Harma (AST2600) BMC Peter Yin
2023-12-04 8:20 ` [PATCH v5 0/2] Add Facebook Minerva " Krzysztof Kozlowski
2023-12-04 8:46 ` PeterYin [this message]
2023-12-04 9:06 ` Krzysztof Kozlowski
2023-12-04 9:14 ` PeterYin
2023-12-04 9:16 ` PeterYin
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=3ff5dcd7-69a3-4098-92c6-ed1e8f0bd8f9@gmail.com \
--to=peteryin.openbmc@gmail.com \
--cc=andrew@aj.id.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patrick@stwcx.xyz \
--cc=robh+dt@kernel.org \
/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