From: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
To: linux-kernel@vger.kernel.org,
Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
linux-renesas-soc@vger.kernel.org,
Duc Nguyen <duc.nguyen.ub@renesas.com>
Subject: Re: [RFC PATCH] memory: renesas-rpc-if: Correct QSPI data transfer in Manual mode
Date: Tue, 28 Sep 2021 12:35:48 +0200 [thread overview]
Message-ID: <163282533892.34438.1878675609177525004.b4-ty@canonical.com> (raw)
In-Reply-To: <20210922091007.5516-1-wsa+renesas@sang-engineering.com>
On Wed, 22 Sep 2021 11:10:06 +0200, Wolfram Sang wrote:
> This patch fixes 2 problems:
> [1] The output warning logs and data loss when performing
> mount/umount then remount the device with jffs2 format.
> [2] The access width of SMWDR[0:1]/SMRDR[0:1] register is wrong.
>
> This is the sample warning logs when performing mount/umount then
> remount the device with jffs2 format:
> jffs2: jffs2_scan_inode_node(): CRC failed on node at 0x031c51d4:
> Read 0x00034e00, calculated 0xadb272a7
>
> [...]
Applied, thanks!
[1/1] memory: renesas-rpc-if: Correct QSPI data transfer in Manual mode
commit: fff53a551db50f5edecaa0b29a64056ab8d2bbca
Best regards,
--
Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
next prev parent reply other threads:[~2021-09-28 10:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 9:10 [RFC PATCH] memory: renesas-rpc-if: Correct QSPI data transfer in Manual mode Wolfram Sang
2021-09-24 11:09 ` Krzysztof Kozlowski
2021-09-24 12:35 ` Wolfram Sang
2021-09-27 8:51 ` Lad, Prabhakar
2021-09-27 9:45 ` Geert Uytterhoeven
2021-09-27 19:50 ` Lad, Prabhakar
2021-09-27 20:10 ` Wolfram Sang
2021-09-28 9:46 ` Krzysztof Kozlowski
2021-09-28 10:31 ` Wolfram Sang
2021-09-28 10:35 ` Krzysztof Kozlowski [this message]
2022-03-07 16:44 ` Geert Uytterhoeven
2022-03-07 17:47 ` Krzysztof Kozlowski
2022-03-07 18:11 ` Geert Uytterhoeven
2022-03-08 8:21 ` Wolfram Sang
2022-03-08 8:29 ` Geert Uytterhoeven
2022-03-08 8:46 ` Wolfram Sang
2022-03-08 9:01 ` Geert Uytterhoeven
2022-03-11 16:55 ` Geert Uytterhoeven
2022-04-27 10:22 ` 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=163282533892.34438.1878675609177525004.b4-ty@canonical.com \
--to=krzysztof.kozlowski@canonical.com \
--cc=duc.nguyen.ub@renesas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--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.