All of lore.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Emil Renner Berthing <kernel@esmil.dk>,
	Conor Dooley <conor@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Paul Walmsley <pjw@kernel.org>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Alexandre Ghiti <alex@ghiti.fr>, E Shattow <e@freeshell.de>
Cc: Conor Dooley <conor.dooley@microchip.com>,
	linux-riscv@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dts: starfive: jh7110-common: split out mmc0 reset pins from common into boards
Date: Mon, 20 Oct 2025 18:36:53 +0100	[thread overview]
Message-ID: <20251020-eel-skipper-c71e1f8fb679@spud> (raw)
In-Reply-To: <20251005174450.1949110-1-e@freeshell.de>

From: Conor Dooley <conor.dooley@microchip.com>

On Sun, 05 Oct 2025 10:44:28 -0700, E Shattow wrote:
> Prepare for Orange Pi RV using jh7110-common.dtsi having GPIO62 assignment
> different than mmc0 reset by splitting this out into each board dts.
> 
> 

Applied to riscv-dt-for-next, thanks!

[1/1] dts: starfive: jh7110-common: split out mmc0 reset pins from common into boards
      https://git.kernel.org/conor/c/fa939a287224

Thanks,
Conor.

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

WARNING: multiple messages have this Message-ID (diff)
From: Conor Dooley <conor@kernel.org>
To: Emil Renner Berthing <kernel@esmil.dk>,
	Conor Dooley <conor@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Paul Walmsley <pjw@kernel.org>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Alexandre Ghiti <alex@ghiti.fr>, E Shattow <e@freeshell.de>
Cc: Conor Dooley <conor.dooley@microchip.com>,
	linux-riscv@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dts: starfive: jh7110-common: split out mmc0 reset pins from common into boards
Date: Mon, 20 Oct 2025 18:36:53 +0100	[thread overview]
Message-ID: <20251020-eel-skipper-c71e1f8fb679@spud> (raw)
In-Reply-To: <20251005174450.1949110-1-e@freeshell.de>

From: Conor Dooley <conor.dooley@microchip.com>

On Sun, 05 Oct 2025 10:44:28 -0700, E Shattow wrote:
> Prepare for Orange Pi RV using jh7110-common.dtsi having GPIO62 assignment
> different than mmc0 reset by splitting this out into each board dts.
> 
> 

Applied to riscv-dt-for-next, thanks!

[1/1] dts: starfive: jh7110-common: split out mmc0 reset pins from common into boards
      https://git.kernel.org/conor/c/fa939a287224

Thanks,
Conor.

  reply	other threads:[~2025-10-20 17:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-05 17:44 [PATCH] dts: starfive: jh7110-common: split out mmc0 reset pins from common into boards E Shattow
2025-10-05 17:44 ` E Shattow
2025-10-20 17:36 ` Conor Dooley [this message]
2025-10-20 17:36   ` Conor Dooley

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=20251020-eel-skipper-c71e1f8fb679@spud \
    --to=conor@kernel.org \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=conor.dooley@microchip.com \
    --cc=devicetree@vger.kernel.org \
    --cc=e@freeshell.de \
    --cc=kernel@esmil.dk \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=pjw@kernel.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.