From: Chia Li Hung <ppighouse@gmail.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: "AllenYY Hsu(許幼岳)" <Allenyy_Hsu@asus.com>,
kelly_hung@asus.com, joel@jms.id.au,
krzysztof.kozlowski+dt@linaro.org, openbmc@lists.ozlabs.org
Subject: Re: [PATCH] ARM: dts: aspeed: asus: Add ASUS X4TF BMC
Date: Tue, 26 Mar 2024 15:57:35 +0800 [thread overview]
Message-ID: <CAK=2Bxs=oAxL+-XY+skwLxmHBB1Tts5wEQ+vejCCtmcDcgGJPA@mail.gmail.com> (raw)
In-Reply-To: <57419138-9c80-46c3-9341-b55576a3f7d2@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 788 bytes --]
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> 於 2024年1月30日 週二
下午6:35寫道：
> On 30/01/2024 09:56, Kelly Hung wrote:
> > This initial device-tree provides the necessary configuration for
> > basic BMC functionality and work on ASUS X4TF production.
> >
> > Signed-off-by: Kelly Hung <Kelly_Hung@asus.com>
>
> Please use subject prefixes matching the subsystem. You can get them for
> example with `git log --oneline -- DIRECTORY_OR_FILE` on the directory
> your patch is touching.
>
> Hi, Krzysztof,
I use my Gmail account and respond inline.
Yes, I used `git log --oneline -- DIRECTORY_OR_FILE` and re-sent the v5
patch on February 29, 2024.
[PATCH v5 1/2] dt-bindings: arm: aspeed: add ASUS X4TF board
> Best regards,
> Krzysztof
>
>
[-- Attachment #2: Type: text/html, Size: 1426 bytes --]
next parent reply other threads:[~2024-03-26 7:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240130085652.198010-1-Kelly_Hung@asus.com>
[not found] ` <57419138-9c80-46c3-9341-b55576a3f7d2@linaro.org>
2024-03-26 7:57 ` Chia Li Hung [this message]
[not found] ` <20240130085652.198010-2-Kelly_Hung@asus.com>
[not found] ` <3edf1a47-9f73-4e99-98ea-182248102346@linaro.org>
2024-03-26 8:10 ` [PATCH] ARM: dts: aspeed: asus: Add ASUS X4TF BMC Chia Li Hung
[not found] ` <TYZPR04MB659655F98C755C9DE55FD4AB9D232@TYZPR04MB6596.apcprd04.prod.outlook.com>
[not found] ` <d2426e1f-a09c-466f-a490-40fb7daf406c@linaro.org>
2024-03-26 8:14 ` Chia Li Hung
2024-01-30 9:04 Kelly Hung
2024-01-30 9:04 ` Kelly Hung
2024-02-01 9:24 ` Krzysztof Kozlowski
2024-03-05 6:30 ` Kelly Hung(洪嘉莉)
2024-03-05 7:09 ` Krzysztof Kozlowski
2024-03-05 9:42 ` Kelly Hung(洪嘉莉)
2024-03-05 9:44 ` Krzysztof Kozlowski
2024-03-05 9:57 ` Chia Li Hung
2024-03-26 8:19 ` Chia Li Hung
2024-03-26 8:43 ` Krzysztof Kozlowski
2024-03-26 10:53 ` Chia Li Hung
2024-03-26 11:29 ` Krzysztof Kozlowski
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='CAK=2Bxs=oAxL+-XY+skwLxmHBB1Tts5wEQ+vejCCtmcDcgGJPA@mail.gmail.com' \
--to=ppighouse@gmail.com \
--cc=Allenyy_Hsu@asus.com \
--cc=joel@jms.id.au \
--cc=kelly_hung@asus.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=openbmc@lists.ozlabs.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).