All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tianling Shen <cnsztl@gmail.com>
To: Quentin Schulz <quentin.schulz@cherry.de>,
	Simon Glass <sjg@chromium.org>,
	Philipp Tomsich <philipp.tomsich@vrull.eu>,
	Kever Yang <kever.yang@rock-chips.com>,
	Jonas Karlman <jonas@kwiboo.se>
Cc: u-boot@lists.denx.de
Subject: Re: [PATCH 0/7] board: rockchip: add FriendlyElec NanoPi R3S
Date: Tue, 14 Jan 2025 22:49:58 +0800	[thread overview]
Message-ID: <5d2fb256-cd0a-4a94-ba9f-f13a928656ed@gmail.com> (raw)
In-Reply-To: <2b658c60-480f-4488-8c40-f781a849cb32@cherry.de>

Hi Quentin,

On 2025/1/14 22:39, Quentin Schulz wrote:
> Hi Tianling,
> 
> On 12/26/24 10:20 AM, Tianling Shen wrote:
>> The NanoPi R3S(as "R3S") is an open source platform with dual-Gbps
>> Ethernet ports designed and developed by FriendlyElec for IoT
>> applications.
>>
>> Tianling Shen (7):
>>    arm64: dts: rockchip: Add FriendlyARM NanoPi R3S board
>>    arm64: dts: rockchip: fix model name for FriendlyElec NanoPi R3S
>>    arm64: dts: rockchip: replace deprecated snps,reset props for NanoPi
>>      R3S
>>    arm64: dts: rockchip: sort props in pmu_io_domains node for NanoPi R3S
>>    arm64: dts: rockchip: enable eMMC HS200 mode for NanoPi R3S
>>    arm64: dts: rockchip: reorder mmc aliases for NanoPi R3S
> 
> How did you backport the above patches?
> 
> ./tools/update-subtree.sh pick dts <commit>
> 
> is the tool to be used, it should have added a
> 

Thank you for the tip! I did not know there's such a script and
I just copy&paste the commit message from linux tree manually.

Thanks,
Tianling.

> (cherry picked from commit ...)
> 
> in the commit log.
> 
> Cheers,
> Quentin


  reply	other threads:[~2025-01-14 14:50 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-26  9:20 [PATCH 0/7] board: rockchip: add FriendlyElec NanoPi R3S Tianling Shen
2024-12-26  9:20 ` [PATCH 1/7] arm64: dts: rockchip: Add FriendlyARM NanoPi R3S board Tianling Shen
2025-01-02  8:44   ` Kever Yang
2024-12-26  9:20 ` [PATCH 2/7] arm64: dts: rockchip: fix model name for FriendlyElec NanoPi R3S Tianling Shen
2025-01-02  8:45   ` Kever Yang
2024-12-26  9:20 ` [PATCH 3/7] arm64: dts: rockchip: replace deprecated snps, reset props for " Tianling Shen
2025-01-02  8:53   ` [PATCH 3/7] arm64: dts: rockchip: replace deprecated snps,reset " Kever Yang
2024-12-26  9:20 ` [PATCH 4/7] arm64: dts: rockchip: sort props in pmu_io_domains node " Tianling Shen
2025-01-02  8:54   ` Kever Yang
2024-12-26  9:20 ` [PATCH 5/7] arm64: dts: rockchip: enable eMMC HS200 mode " Tianling Shen
2025-01-02  8:54   ` Kever Yang
2024-12-26  9:20 ` [PATCH 6/7] arm64: dts: rockchip: reorder mmc aliases " Tianling Shen
2025-01-02  8:55   ` Kever Yang
2024-12-26  9:20 ` [PATCH 7/7] board: rockchip: add FriendlyElec " Tianling Shen
2025-01-02  8:55   ` Kever Yang
2025-01-06  3:06   ` Kever Yang
2025-01-06  4:39     ` Tianling Shen
2025-01-14 14:48   ` Quentin Schulz
2025-01-14 15:03     ` Tianling Shen
2025-01-14 14:39 ` [PATCH 0/7] " Quentin Schulz
2025-01-14 14:49   ` Tianling Shen [this message]
2025-01-14 15:21     ` Quentin Schulz
2025-01-14 16:14       ` Tianling Shen
2025-01-15 11:17         ` Quentin Schulz

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=5d2fb256-cd0a-4a94-ba9f-f13a928656ed@gmail.com \
    --to=cnsztl@gmail.com \
    --cc=jonas@kwiboo.se \
    --cc=kever.yang@rock-chips.com \
    --cc=philipp.tomsich@vrull.eu \
    --cc=quentin.schulz@cherry.de \
    --cc=sjg@chromium.org \
    --cc=u-boot@lists.denx.de \
    /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.