From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
Vignesh Raghavendra <vigneshr@ti.com>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Mark Brown <broonie@kernel.org>
Cc: Philipp Zabel <p.zabel@pengutronix.de>,
Sergey Shtylyov <s.shtylyov@omp.ru>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org,
linux-spi@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v2 0/6] memory: renesas-rpc-if: Rebind fixes and misc cleanups
Date: Sun, 27 Nov 2022 22:34:42 +0100 [thread overview]
Message-ID: <a75b604c-a671-d2c5-7160-74dcb8a4fa2e@linaro.org> (raw)
In-Reply-To: <b500e42c-f782-79c6-70ce-650e4ea32c54@linaro.org>
On 27/11/2022 22:31, Krzysztof Kozlowski wrote:
> On 23/11/2022 15:41, Geert Uytterhoeven wrote:
>> Hi all,
>>
>> The Renesas RPC-IF provides either HyperFlash or SPI host access.
>> To handle this, three drivers are used:
>> 1. The RPC-IF core diver,
>> 2. An HyperFlash child driver,
>> 3. An SPI child driver.
>>
>
> Thank you for the patch.
> It is too late in the cycle for me to pick it up. I will take it after
> the merge window.
Optionally, if you want to push it via Renesas SoC tree and there are no
conflicts with existing two patches, then these look good:
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Otherwise, I'll pick them up after the merge window.
Best regards,
Krzysztof
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
WARNING: multiple messages have this Message-ID (diff)
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
Vignesh Raghavendra <vigneshr@ti.com>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Mark Brown <broonie@kernel.org>
Cc: Philipp Zabel <p.zabel@pengutronix.de>,
Sergey Shtylyov <s.shtylyov@omp.ru>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org,
linux-spi@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v2 0/6] memory: renesas-rpc-if: Rebind fixes and misc cleanups
Date: Sun, 27 Nov 2022 22:34:42 +0100 [thread overview]
Message-ID: <a75b604c-a671-d2c5-7160-74dcb8a4fa2e@linaro.org> (raw)
In-Reply-To: <b500e42c-f782-79c6-70ce-650e4ea32c54@linaro.org>
On 27/11/2022 22:31, Krzysztof Kozlowski wrote:
> On 23/11/2022 15:41, Geert Uytterhoeven wrote:
>> Hi all,
>>
>> The Renesas RPC-IF provides either HyperFlash or SPI host access.
>> To handle this, three drivers are used:
>> 1. The RPC-IF core diver,
>> 2. An HyperFlash child driver,
>> 3. An SPI child driver.
>>
>
> Thank you for the patch.
> It is too late in the cycle for me to pick it up. I will take it after
> the merge window.
Optionally, if you want to push it via Renesas SoC tree and there are no
conflicts with existing two patches, then these look good:
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Otherwise, I'll pick them up after the merge window.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-11-27 21:35 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 14:41 [PATCH v2 0/6] memory: renesas-rpc-if: Rebind fixes and misc cleanups Geert Uytterhoeven
2022-11-23 14:41 ` Geert Uytterhoeven
2022-11-23 14:41 ` [PATCH v2 1/6] memory: renesas-rpc-if: Split-off private data from struct rpcif Geert Uytterhoeven
2022-11-23 14:41 ` Geert Uytterhoeven
2022-11-23 14:41 ` [PATCH v2 2/6] memory: renesas-rpc-if: Move resource acquisition to .probe() Geert Uytterhoeven
2022-11-23 14:41 ` Geert Uytterhoeven
2022-11-23 14:41 ` [PATCH v2 3/6] memory: renesas-rpc-if: Always use dev in rpcif_probe() Geert Uytterhoeven
2022-11-23 14:41 ` Geert Uytterhoeven
2022-11-23 14:41 ` [PATCH v2 4/6] memory: renesas-rpc-if: Improve Runtime PM handling Geert Uytterhoeven
2022-11-23 14:41 ` Geert Uytterhoeven
2022-11-23 14:41 ` [PATCH v2 5/6] memory: renesas-rpc-if: Pass device instead of rpcif to rpcif_*() Geert Uytterhoeven
2022-11-23 14:41 ` Geert Uytterhoeven
2022-11-23 14:43 ` Mark Brown
2022-11-23 14:43 ` Mark Brown
2022-11-23 14:41 ` [PATCH v2 6/6] memory: renesas-rpc-if: Remove Runtime PM wrappers Geert Uytterhoeven
2022-11-23 14:41 ` Geert Uytterhoeven
2022-11-27 21:31 ` [PATCH v2 0/6] memory: renesas-rpc-if: Rebind fixes and misc cleanups Krzysztof Kozlowski
2022-11-27 21:31 ` Krzysztof Kozlowski
2022-11-27 21:34 ` Krzysztof Kozlowski [this message]
2022-11-27 21:34 ` Krzysztof Kozlowski
2022-11-28 7:37 ` Geert Uytterhoeven
2022-11-28 7:37 ` Geert Uytterhoeven
2022-12-05 8:56 ` Wolfram Sang
2022-12-05 8:56 ` Wolfram Sang
2022-12-27 8:59 ` Krzysztof Kozlowski
2022-12-27 8:59 ` Krzysztof Kozlowski
2022-12-27 9:06 ` Krzysztof Kozlowski
2022-12-27 9:06 ` Krzysztof Kozlowski
2022-12-27 9:09 ` Geert Uytterhoeven
2022-12-27 9:09 ` Geert Uytterhoeven
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=a75b604c-a671-d2c5-7160-74dcb8a4fa2e@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=broonie@kernel.org \
--cc=geert+renesas@glider.be \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=p.zabel@pengutronix.de \
--cc=richard@nod.at \
--cc=s.shtylyov@omp.ru \
--cc=vigneshr@ti.com \
--cc=wsa+renesas@sang-engineering.com \
/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.