From: Kelly Hung <ppighouse@gmail.com>
To: robh+dt@kernel.org
Cc: krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
joel@jms.id.au, andrew@codeconstruct.com.au,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
openbmc@lists.ozlabs.org, kelly_hung@asus.com,
Allenyy_Hsu@asus.com, Kelly Hung <Kelly_Hung@asus.com>
Subject: [PATCH v7 0/2] modify Signed-off-by field
Date: Tue, 30 Apr 2024 12:58:51 +0800 [thread overview]
Message-ID: <20240430045853.3894633-1-Kelly_Hung@asus.com> (raw)
For the warning message:
From: Kelly Hung '<ppighouse@gmail.com>' != 'Signed-off-by: Kelly Hung
<Kelly_Hung@asus.com>'
I replaced Kelly_Hung@asus.com with my private Gmail account.
Due to a security issue with ASUS's mail server, I am unable to use
ASUS's mail system to send patches out from my build server.
So I executed git send-email using my private gmail accoutt.
Kelly Hung (2):
dt-bindings: arm: aspeed: add ASUS X4TF board
ARM: dts: aspeed: x4tf: Add dts for asus x4tf project
.../bindings/arm/aspeed/aspeed.yaml | 1 +
arch/arm/boot/dts/aspeed/Makefile | 1 +
.../boot/dts/aspeed/aspeed-bmc-asus-x4tf.dts | 581 ++++++++++++++++++
3 files changed, 583 insertions(+)
create mode 100644 arch/arm/boot/dts/aspeed/aspeed-bmc-asus-x4tf.dts
--
2.25.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2024-04-30 4:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-30 4:58 Kelly Hung [this message]
2024-04-30 4:58 ` [PATCH v7 1/2] dt-bindings: arm: aspeed: add ASUS X4TF board Kelly Hung
2024-04-30 8:35 ` Conor Dooley
2024-04-30 4:58 ` [PATCH v7 2/2] ARM: dts: aspeed: x4tf: Add dts for asus x4tf project Kelly Hung
2024-04-30 6:48 ` [PATCH v7 0/2] modify Signed-off-by field Paul Menzel
[not found] ` <CAK=2Bxt=WK4AdktNZDN2iXjk3ga9WRqUm9JQHoNjRnrW8hVt0Q@mail.gmail.com>
2024-04-30 10:21 ` Paul Menzel
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=20240430045853.3894633-1-Kelly_Hung@asus.com \
--to=ppighouse@gmail.com \
--cc=Allenyy_Hsu@asus.com \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=kelly_hung@asus.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--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;
as well as URLs for NNTP newsgroup(s).