From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Christian Marangi <ansuelsmth@gmail.com>
Cc: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
linux-mtd@lists.infradead.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mtd: rawnand: qcom: finish converting register to FIELD_PREP
Date: Mon, 10 Feb 2025 16:15:38 +0100 [thread overview]
Message-ID: <877c5xu8yt.fsf@bootlin.com> (raw)
In-Reply-To: <20250209145439.19047-1-ansuelsmth@gmail.com> (Christian Marangi's message of "Sun, 9 Feb 2025 15:54:32 +0100")
Hello Christian,
On 09/02/2025 at 15:54:32 +01, Christian Marangi <ansuelsmth@gmail.com> wrote:
> With some research in some obscure old QSDK, it was possible to find the
> MASK of the last register there were still set with raw shift and
> convert them to FIELD_PREP API.
>
> This is only a cleanup and modernize the code a bit and doesn't make
> any behaviour change.
>
> Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
> ---
> drivers/mtd/nand/raw/qcom_nandc.c | 36 ++++++++++++++--------------
I'm fine with your two patches. I was about to apply them, but the first
one needs to go through fixes, whereas the second through next, and they
are dependent on each other. I propose the following modification:
- create patch 1/2 with the content of the cleanup done just below, but
only adapted to the very specific spot that is touched by the fix "fix
broken config...". It would be a prerequisite for the fix.
- patch 2/2 would be the content of "fix broken config..."
And aside, a totally independent patch easy to apply on -rc1 with the
rest of this patch.
Would that work for you?
Thanks,
Miquèl
WARNING: multiple messages have this Message-ID (diff)
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Christian Marangi <ansuelsmth@gmail.com>
Cc: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
linux-mtd@lists.infradead.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mtd: rawnand: qcom: finish converting register to FIELD_PREP
Date: Mon, 10 Feb 2025 16:15:38 +0100 [thread overview]
Message-ID: <877c5xu8yt.fsf@bootlin.com> (raw)
In-Reply-To: <20250209145439.19047-1-ansuelsmth@gmail.com> (Christian Marangi's message of "Sun, 9 Feb 2025 15:54:32 +0100")
Hello Christian,
On 09/02/2025 at 15:54:32 +01, Christian Marangi <ansuelsmth@gmail.com> wrote:
> With some research in some obscure old QSDK, it was possible to find the
> MASK of the last register there were still set with raw shift and
> convert them to FIELD_PREP API.
>
> This is only a cleanup and modernize the code a bit and doesn't make
> any behaviour change.
>
> Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
> ---
> drivers/mtd/nand/raw/qcom_nandc.c | 36 ++++++++++++++--------------
I'm fine with your two patches. I was about to apply them, but the first
one needs to go through fixes, whereas the second through next, and they
are dependent on each other. I propose the following modification:
- create patch 1/2 with the content of the cleanup done just below, but
only adapted to the very specific spot that is touched by the fix "fix
broken config...". It would be a prerequisite for the fix.
- patch 2/2 would be the content of "fix broken config..."
And aside, a totally independent patch easy to apply on -rc1 with the
rest of this patch.
Would that work for you?
Thanks,
Miquèl
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2025-02-10 15:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-09 14:54 [PATCH] mtd: rawnand: qcom: finish converting register to FIELD_PREP Christian Marangi
2025-02-09 14:54 ` Christian Marangi
2025-02-10 15:15 ` Miquel Raynal [this message]
2025-02-10 15:15 ` Miquel Raynal
2025-02-10 20:44 ` Christian Marangi
2025-02-10 20:44 ` Christian Marangi
2025-02-11 10:55 ` Miquel Raynal
2025-02-11 10:55 ` Miquel Raynal
2025-02-11 12:55 ` Miquel Raynal
2025-02-11 12:55 ` Miquel Raynal
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=877c5xu8yt.fsf@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=ansuelsmth@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=manivannan.sadhasivam@linaro.org \
--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 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.