All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: Chukun Pan <amadeus@jmu.edu.cn>
Cc: amadeus@jmu.edu.cn, conor+dt@kernel.org,
	devicetree@vger.kernel.org, krzk+dt@kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
	robh@kernel.org
Subject: Re: (subset) [PATCH 1/6] arm64: dts: rockchip: add mmc aliases for 100ASK DshanPi A1
Date: Sat, 15 Nov 2025 20:53:12 +0100	[thread overview]
Message-ID: <2251982.Mh6RI2rZIc@diego> (raw)
In-Reply-To: <20251115150010.1052575-1-amadeus@jmu.edu.cn>

Hi,

Am Samstag, 15. November 2025, 16:00:10 Mitteleuropäische Normalzeit schrieb Chukun Pan:
> > Applied, thanks!
> 
> > [4/6] arm64: dts: rockchip: fixes supply for 100ASK DshanPi A1
> >       commit: 621bb09a76fa12a9e61c9d745ae524db86abf781
> 
> Sorry, I don't know if this is a problem:
> 
> The commit message started with an extra ">".
> 
> >From the schematic, the supply of ES8388 chip and the vmmc-supply
> of SD card both originate from the VCC3V3_S0 regulator, fix it.
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git/commit/?id=621bb09a76fa12a9e61c9d745ae524db86abf781

thanks for noticing this. I've now edited the commit message in place
to fix that.

Heiko




WARNING: multiple messages have this Message-ID (diff)
From: "Heiko Stübner" <heiko@sntech.de>
To: Chukun Pan <amadeus@jmu.edu.cn>
Cc: amadeus@jmu.edu.cn, conor+dt@kernel.org,
	devicetree@vger.kernel.org, krzk+dt@kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
	robh@kernel.org
Subject: Re: (subset) [PATCH 1/6] arm64: dts: rockchip: add mmc aliases for 100ASK DshanPi A1
Date: Sat, 15 Nov 2025 20:53:12 +0100	[thread overview]
Message-ID: <2251982.Mh6RI2rZIc@diego> (raw)
In-Reply-To: <20251115150010.1052575-1-amadeus@jmu.edu.cn>

Hi,

Am Samstag, 15. November 2025, 16:00:10 Mitteleuropäische Normalzeit schrieb Chukun Pan:
> > Applied, thanks!
> 
> > [4/6] arm64: dts: rockchip: fixes supply for 100ASK DshanPi A1
> >       commit: 621bb09a76fa12a9e61c9d745ae524db86abf781
> 
> Sorry, I don't know if this is a problem:
> 
> The commit message started with an extra ">".
> 
> >From the schematic, the supply of ES8388 chip and the vmmc-supply
> of SD card both originate from the VCC3V3_S0 regulator, fix it.
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git/commit/?id=621bb09a76fa12a9e61c9d745ae524db86abf781

thanks for noticing this. I've now edited the commit message in place
to fix that.

Heiko



_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip

  reply	other threads:[~2025-11-15 19:53 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-01 12:00 [PATCH 1/6] arm64: dts: rockchip: add mmc aliases for 100ASK DshanPi A1 Chukun Pan
2025-11-01 12:00 ` Chukun Pan
2025-11-01 12:00 ` [PATCH 2/6] arm64: dts: rockchip: fixes regulator " Chukun Pan
2025-11-01 12:00   ` Chukun Pan
2025-11-01 12:00 ` [PATCH 3/6] arm64: dts: rockchip: fixes ethernet " Chukun Pan
2025-11-01 12:00   ` Chukun Pan
2025-11-01 12:00 ` [PATCH 4/6] arm64: dts: rockchip: fixes supply " Chukun Pan
2025-11-01 12:00   ` Chukun Pan
2025-11-01 12:00 ` [PATCH 5/6] arm64: dts: rockchip: fixes audio " Chukun Pan
2025-11-01 12:00   ` Chukun Pan
2025-11-01 12:00 ` [PATCH 6/6] arm64: dts: rockchip: update 100ASK DshanPi A1 support Chukun Pan
2025-11-01 12:00   ` Chukun Pan
2025-11-13 23:05   ` Heiko Stübner
2025-11-13 23:05     ` Heiko Stübner
2025-11-13 23:00 ` [PATCH 1/6] arm64: dts: rockchip: add mmc aliases for 100ASK DshanPi A1 Heiko Stübner
2025-11-13 23:00   ` Heiko Stübner
2025-11-13 23:04 ` (subset) " Heiko Stuebner
2025-11-13 23:04   ` Heiko Stuebner
2025-11-15 15:00   ` Chukun Pan
2025-11-15 15:00     ` Chukun Pan
2025-11-15 19:53     ` Heiko Stübner [this message]
2025-11-15 19:53       ` Heiko Stübner

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=2251982.Mh6RI2rZIc@diego \
    --to=heiko@sntech.de \
    --cc=amadeus@jmu.edu.cn \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --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.