From: Mark Brown <broonie@kernel.org>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: "Nícolas F. R. A. Prado" <nfraprado@collabora.com>,
linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
"Neil Armstrong" <neil.armstrong@linaro.org>
Subject: Re: [PATCH v1 0/2] spi: Make dummy SG handling robust
Date: Mon, 3 Jun 2024 13:26:36 +0100 [thread overview]
Message-ID: <c258a169-cdbc-4a92-bae6-46bd38df86fb@sirena.org.uk> (raw)
In-Reply-To: <CAHp75VehYoEFPV4jTdXh4D5DSGUkHzska6tuvB=BrZDpZhiv5Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 398 bytes --]
On Sat, Jun 01, 2024 at 12:45:30AM +0300, Andy Shevchenko wrote:
> I have sent a new series where the last patch has a massive rework of
> the cur_msg_mapped flag. Would be nice to see if it passes your tests.
> The main idea there is to actually move to per transfer flag(s) from
> per message one.
That feels like a sensible cleanup but also a bit much for a fix with
all the driver updates...
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-06-03 12:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-31 9:44 Andy Shevchenko
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 [this message]
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=c258a169-cdbc-4a92-bae6-46bd38df86fb@sirena.org.uk \
--to=broonie@kernel.org \
--cc=andy.shevchenko@gmail.com \
--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
all inboxes | Powered by JetHome®