Linux Renesas SOC kernel development
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Biju Das <biju.das.jz@bp.renesas.com>,
	Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
	Mark Brown <broonie@kernel.org>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Magnus Damm <magnus.damm@gmail.com>
Cc: devicetree@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
	linux-spi@vger.kernel.org,
	Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
	Biju Das <biju.das.au@gmail.com>
Subject: Re: [PATCH v5 0/7] Add RZ/G3E xSPI support
Date: Thu, 1 May 2025 12:23:35 +0200	[thread overview]
Message-ID: <00f58dfb-7b23-4b4d-a551-9cbc5b800bf6@kernel.org> (raw)
In-Reply-To: <20250424090000.136804-1-biju.das.jz@bp.renesas.com>

On 24/04/2025 10:59, Biju Das wrote:
> Biju Das (7):
>   dt-bindings: memory: Document RZ/G3E support
>   memory: renesas-rpc-if: Move rpc-if reg definitions
>   memory: renesas-rpc-if: Use devm_reset_control_array_get_exclusive()
>   memory: renesas-rpc-if: Add regmap to struct rpcif_info
>   memory: renesas-rpc-if: Add wrapper functions
>   memory: renesas-rpc-if: Add RZ/G3E xSPI support
>   spi: rpc-if: Add write support for memory-mapped area

Mark,

I will prepare you a stable tag for spi once everything gets processed
by linux-next.

Best regards,
Krzysztof

  parent reply	other threads:[~2025-05-01 10:23 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-24  8:59 [PATCH v5 0/7] Add RZ/G3E xSPI support Biju Das
2025-04-24  8:59 ` [PATCH v5 1/7] dt-bindings: memory: Document RZ/G3E support Biju Das
2025-05-01 10:25   ` (subset) " Krzysztof Kozlowski
2025-04-24  8:59 ` [PATCH v5 2/7] memory: renesas-rpc-if: Move rpc-if reg definitions Biju Das
2025-04-30 18:46   ` Krzysztof Kozlowski
2025-05-01  5:42     ` Biju Das
2025-05-01 10:16       ` Krzysztof Kozlowski
2025-05-01 10:25   ` (subset) " Krzysztof Kozlowski
2025-04-24  8:59 ` [PATCH v5 3/7] memory: renesas-rpc-if: Use devm_reset_control_array_get_exclusive() Biju Das
2025-04-30 18:46   ` Krzysztof Kozlowski
2025-05-01  5:56     ` Biju Das
2025-05-01 10:21       ` Krzysztof Kozlowski
2025-05-01 10:25   ` (subset) " Krzysztof Kozlowski
2025-04-24  8:59 ` [PATCH v5 4/7] memory: renesas-rpc-if: Add regmap to struct rpcif_info Biju Das
2025-05-01 10:25   ` (subset) " Krzysztof Kozlowski
2025-04-24  8:59 ` [PATCH v5 5/7] memory: renesas-rpc-if: Add wrapper functions Biju Das
2025-05-01 10:25   ` (subset) " Krzysztof Kozlowski
2025-04-24  8:59 ` [PATCH v5 6/7] memory: renesas-rpc-if: Add RZ/G3E xSPI support Biju Das
2025-05-01 10:25   ` (subset) " Krzysztof Kozlowski
2025-04-24  8:59 ` [PATCH v5 7/7] spi: rpc-if: Add write support for memory-mapped area Biju Das
2025-05-08  9:08   ` Krzysztof Kozlowski
2025-05-01 10:23 ` Krzysztof Kozlowski [this message]
2025-05-10  1:51 ` (subset) [PATCH v5 0/7] Add RZ/G3E xSPI support Mark Brown

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=00f58dfb-7b23-4b4d-a551-9cbc5b800bf6@kernel.org \
    --to=krzk@kernel.org \
    --cc=biju.das.au@gmail.com \
    --cc=biju.das.jz@bp.renesas.com \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox