From: Linus Walleij <linus.walleij@linaro.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
Ulf Hansson <ulf.hansson@linaro.org>
Cc: linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: [PATCH v2 0/2] Try to fix the sg_mitet bugs in SH MMCIF
Date: Wed, 21 Feb 2024 22:22:59 +0100 [thread overview]
Message-ID: <20240221-fix-sh-mmcif-v2-0-5e521eb25ae4@linaro.org> (raw)
This adresses some bugs found after the introduction of the
memory iterator sg_miter to the sh mmcif driver.
This was first just one patch for fixing the atomic bug, but
now also a second patch is needed to fix a semantic issue.
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
---
Changes in v2:
- Collect Geerts test tag on patch 1
- Add a second patch fixing the problem with advancing to
the next sglist entry before reading/writing the first block and
after reading/writing each block in a multiblock operation.
- Link to v1: https://lore.kernel.org/r/20240220-fix-sh-mmcif-v1-1-b9d08a787c1f@linaro.org
---
Linus Walleij (2):
mmc: sh_mmcif: sg_miter does not need to be atomic
mmc: sh_mmcif: Advance sg_miter before reading blocks
drivers/mmc/host/sh_mmcif.c | 46 +++++++++++++++++++++++++++++----------------
1 file changed, 30 insertions(+), 16 deletions(-)
---
base-commit: 2d5c7b7eb345249cb34d42cbc2b97b4c57ea944e
change-id: 20240220-fix-sh-mmcif-49c1de70c5b7
Best regards,
--
Linus Walleij <linus.walleij@linaro.org>
next reply other threads:[~2024-02-21 21:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 21:22 Linus Walleij [this message]
2024-02-21 21:23 ` [PATCH v2 1/2] mmc: sh_mmcif: sg_miter does not need to be atomic Linus Walleij
2024-02-22 9:19 ` Geert Uytterhoeven
2024-02-21 21:23 ` [PATCH v2 2/2] mmc: sh_mmcif: Advance sg_miter before reading blocks Linus Walleij
2024-02-22 9:20 ` Geert Uytterhoeven
2024-02-28 13:03 ` [PATCH v2 0/2] Try to fix the sg_mitet bugs in SH MMCIF Ulf Hansson
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=20240221-fix-sh-mmcif-v2-0-5e521eb25ae4@linaro.org \
--to=linus.walleij@linaro.org \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=ulf.hansson@linaro.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).