From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Mark Brown <broonie@kernel.org>,
linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: "Nícolas F . R . A . Prado" <nfraprado@collabora.com>,
"Neil Armstrong" <neil.armstrong@linaro.org>,
"Andy Shevchenko" <andy.shevchenko@gmail.com>
Subject: [PATCH v1 0/2] spi: Make dummy SG handling robust
Date: Fri, 31 May 2024 12:44:31 +0300 [thread overview]
Message-ID: <20240531094658.1598969-1-andy.shevchenko@gmail.com> (raw)
There's an unreliable code to handle DMA mappings on unidirection transfers.
This series does two things:
- it reverts the seemingly unnecessary change
- it reworks dummy SG list handling
There is no need to backport that AFAIU, but no harm to apply for v6.10 aka
the current release cycle. Guys, please test these.
Andy Shevchenko (2):
spi: Revert "Check if transfer is mapped before calling DMA sync APIs"
spi: Do not rely on the SG table and respective API implementations
drivers/spi/spi.c | 46 +++++++++++++++++-----------------------------
1 file changed, 17 insertions(+), 29 deletions(-)
--
2.45.1
next reply other threads:[~2024-05-31 9:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-31 9:44 Andy Shevchenko [this message]
2024-05-31 9:44 ` [PATCH v1 1/2] spi: Revert "Check if transfer is mapped before calling DMA sync APIs" Andy Shevchenko
2024-05-31 12:15 ` Mark Brown
2024-05-31 13:10 ` Andy Shevchenko
2024-05-31 9:44 ` [PATCH v1 2/2] spi: Do not rely on the SG table and respective API implementations Andy Shevchenko
2024-05-31 14:37 ` [PATCH v1 0/2] spi: Make dummy SG handling robust Nícolas F. R. A. Prado
2024-05-31 15:46 ` Andy Shevchenko
2024-05-31 15:51 ` Andy Shevchenko
2024-05-31 17:14 ` Nícolas F. R. A. Prado
2024-05-31 21:45 ` Andy Shevchenko
2024-05-31 21:59 ` Nícolas F. R. A. Prado
2024-06-03 12:26 ` Mark Brown
2024-06-03 17:37 ` Nícolas F. R. A. Prado
2024-06-03 17:44 ` Mark Brown
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=20240531094658.1598969-1-andy.shevchenko@gmail.com \
--to=andy.shevchenko@gmail.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=nfraprado@collabora.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;
as well as URLs for NNTP newsgroup(s).