mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Nícolas F. R. A. Prado" <nfraprado@collabora.com>
To: Mark Brown <broonie@kernel.org>
Cc: Andy Shevchenko <andy.shevchenko@gmail.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:37:02 -0400	[thread overview]
Message-ID: <e5c5edcb-e07b-4400-86ca-4d9a7fe4fc0c@notapiano> (raw)
In-Reply-To: <c258a169-cdbc-4a92-bae6-46bd38df86fb@sirena.org.uk>

On Mon, Jun 03, 2024 at 01:26:36PM +0100, Mark Brown wrote:
> 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...

The current state of linux-next works fine, so there's nothing to fix. That
series is really a cleanup series, since the fix merged wasn't the cleanest
solution possible. (I'll be testing it shortly and posting the feedback there)

Thanks,
Nícolas

  reply	other threads:[~2024-06-03 17:37 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
2024-06-03 17:37             ` Nícolas F. R. A. Prado [this message]
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=e5c5edcb-e07b-4400-86ca-4d9a7fe4fc0c@notapiano \
    --to=nfraprado@collabora.com \
    --cc=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 \
    /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®