From: Michael Opdenacker <michael.opdenacker@rootcommit.com>
To: Dragan Simic <dsimic@manjaro.org>
Cc: michael.opdenacker@rootcommit.com, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, heiko@sntech.de,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] arm64: dts: rockchip: Add Asus Tinker Board 3 and 3S device tree
Date: Sat, 15 Nov 2025 06:03:31 +0000 (UTC) [thread overview]
Message-ID: <bb74679a-ce21-4373-bcc5-1214e9bf832e@rootcommit.com> (raw)
In-Reply-To: <12d6e151-dfa0-ca0a-5888-ddffb2dbdec7@manjaro.org>
Hi Dragan,
Thanks one more time for the reviews, much appreciated :)
On 11/15/25 01:53, Dragan Simic wrote:
> Hello Michael,
>
> Thanks for the v2! Please, see one nitpick below.
>
> On Friday, November 14, 2025 16:46 CET, michael.opdenacker@rootcommit.com wrote:
>> From: Michael Opdenacker <michael.opdenacker@rootcommit.com>
> I'm sorry for not mentioning it in my earlier responses, but this
> line is redundant, because it duplicates the From value found in
> the actual email message.
This actually comes from my Git settings. I need this when I send
patches to the Yocto project and OpenEmbedded. That's because their
mailing list server which alters the address of senders ("<sender> via
lists.yoctoproject.org"), and ultimately the commit author identity in
Git. See
https://docs.yoctoproject.org/contributor-guide/submit-changes.html#fixing-your-from-identity
I've checked that my patches apply fine and that this "From:" line
doesn't appear in the commits in the tree.
So, can I keep this?
:D
Thanks again
Michael.
--
Michael Opdenacker
Root Commit
Embedded Linux Training and Consulting
https://rootcommit.com
WARNING: multiple messages have this Message-ID (diff)
From: Michael Opdenacker <michael.opdenacker@rootcommit.com>
To: Dragan Simic <dsimic@manjaro.org>
Cc: michael.opdenacker@rootcommit.com, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, heiko@sntech.de,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] arm64: dts: rockchip: Add Asus Tinker Board 3 and 3S device tree
Date: Sat, 15 Nov 2025 06:03:31 +0000 (UTC) [thread overview]
Message-ID: <bb74679a-ce21-4373-bcc5-1214e9bf832e@rootcommit.com> (raw)
In-Reply-To: <12d6e151-dfa0-ca0a-5888-ddffb2dbdec7@manjaro.org>
Hi Dragan,
Thanks one more time for the reviews, much appreciated :)
On 11/15/25 01:53, Dragan Simic wrote:
> Hello Michael,
>
> Thanks for the v2! Please, see one nitpick below.
>
> On Friday, November 14, 2025 16:46 CET, michael.opdenacker@rootcommit.com wrote:
>> From: Michael Opdenacker <michael.opdenacker@rootcommit.com>
> I'm sorry for not mentioning it in my earlier responses, but this
> line is redundant, because it duplicates the From value found in
> the actual email message.
This actually comes from my Git settings. I need this when I send
patches to the Yocto project and OpenEmbedded. That's because their
mailing list server which alters the address of senders ("<sender> via
lists.yoctoproject.org"), and ultimately the commit author identity in
Git. See
https://docs.yoctoproject.org/contributor-guide/submit-changes.html#fixing-your-from-identity
I've checked that my patches apply fine and that this "From:" line
doesn't appear in the commits in the tree.
So, can I keep this?
:D
Thanks again
Michael.
--
Michael Opdenacker
Root Commit
Embedded Linux Training and Consulting
https://rootcommit.com
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2025-11-15 6:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-15 0:53 [PATCH v2 2/2] arm64: dts: rockchip: Add Asus Tinker Board 3 and 3S device tree Dragan Simic
2025-11-15 0:53 ` Dragan Simic
2025-11-15 6:03 ` Michael Opdenacker [this message]
2025-11-15 6:03 ` Michael Opdenacker
2025-11-15 7:14 ` Dragan Simic
2025-11-15 7:14 ` Dragan Simic
2025-11-15 23:27 ` Heiko Stübner
2025-11-15 23:27 ` Heiko Stübner
2025-11-17 1:17 ` Dragan Simic
2025-11-17 1:17 ` Dragan Simic
-- strict thread matches above, loose matches on Subject: below --
2025-11-14 15:46 [PATCH v2 0/2] arm64: dts: rockchip: add " michael.opdenacker
2025-11-14 15:46 ` [PATCH v2 2/2] arm64: dts: rockchip: Add Asus " michael.opdenacker
2025-11-14 15:46 ` michael.opdenacker
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=bb74679a-ce21-4373-bcc5-1214e9bf832e@rootcommit.com \
--to=michael.opdenacker@rootcommit.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dsimic@manjaro.org \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.