From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Md Sadre Alam <quic_mdalam@quicinc.com>,
mani@kernel.org, miquel.raynal@bootlin.com, richard@nod.at,
vigneshr@ti.com, linux-mtd@lists.infradead.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: quic_srichara@quicinc.com
Subject: Re: [PATCH 3/3] mtd: rawnand: qcom: Add read/read_start ops in exec_op path
Date: Fri, 18 Aug 2023 22:02:32 +0200 [thread overview]
Message-ID: <20230818200232.149295-1-miquel.raynal@bootlin.com> (raw)
In-Reply-To: <20230818145101.23825-4-quic_mdalam@quicinc.com>
On Fri, 2023-08-18 at 14:51:01 UTC, Md Sadre Alam wrote:
> From: Sricharan Ramabadhran <quic_srichara@quicinc.com>
>
> READ/READ_START opcodes are not set in exec_op path.
> Fixing that here.
>
> While there, Steps to program the controller is common for
> erase/reset/read/program page. So use a common pattern and
> pull them under one function.
>
> Signed-off-by: Md Sadre Alam <quic_mdalam@quicinc.com>
> Signed-off-by: Sricharan Ramabadhran <quic_srichara@quicinc.com>
Applied to https://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git nand/next, thanks.
Miquel
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2023-08-18 20:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 14:50 [PATCH 0/3]mtd: rawnand: qcom: Fixes for exec_op Md Sadre Alam
2023-08-18 14:50 ` [PATCH 1/3] mtd: rawnand: qcom: Update read_loc size to 512 Md Sadre Alam
2023-08-18 19:59 ` Miquel Raynal
2023-08-21 5:30 ` Md Sadre Alam
2023-08-18 14:51 ` [PATCH 2/3] mtd: rawnand: qcom: Clear buf_count and buf_start in raw read Md Sadre Alam
2023-08-18 20:02 ` Miquel Raynal
2023-08-18 14:51 ` [PATCH 3/3] mtd: rawnand: qcom: Add read/read_start ops in exec_op path Md Sadre Alam
2023-08-18 20:02 ` Miquel Raynal [this message]
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=20230818200232.149295-1-miquel.raynal@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mani@kernel.org \
--cc=quic_mdalam@quicinc.com \
--cc=quic_srichara@quicinc.com \
--cc=richard@nod.at \
--cc=vigneshr@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox