From: Mark Brown <broonie@kernel.org>
To: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: Re: [PATCH v1 0/2] soi: Don't call DMA sync API when not needed
Date: Thu, 23 May 2024 16:56:11 +0100 [thread overview]
Message-ID: <171647977136.55224.8875410677372985509.b4-ty@kernel.org> (raw)
In-Reply-To: <20240522171018.3362521-1-andriy.shevchenko@linux.intel.com>
On Wed, 22 May 2024 20:09:48 +0300, Andy Shevchenko wrote:
> A couple of fixes to avoid calling DMA sync API when it's not needed.
> This doesn't stop from discussing if IOMMU code is doing the right thing,
> i.e. dereferences SG list when orig_nents == 0, but this is a separate
> story.
>
> Andy Shevchenko (2):
> spi: Don't mark message DMA mapped when no transfer in it is
> spi: Check if transfer is mapped before calling DMA sync APIs
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/2] spi: Don't mark message DMA mapped when no transfer in it is
commit: 9f788ba457b45b0ce422943fcec9fa35c4587764
[2/2] spi: Check if transfer is mapped before calling DMA sync APIs
commit: da560097c05612f8d360f86528f6213629b9c395
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
prev parent reply other threads:[~2024-05-23 15:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-22 17:09 Andy Shevchenko
2024-05-22 17:09 ` [PATCH v1 1/2] spi: Don't mark message DMA mapped when no transfer in it is Andy Shevchenko
2024-05-22 17:09 ` [PATCH v1 2/2] spi: Check if transfer is mapped before calling DMA sync APIs Andy Shevchenko
2024-05-22 18:41 ` Nícolas F. R. A. Prado
2024-05-23 12:01 ` Mark Brown
2024-05-29 12:35 ` Nícolas F. R. A. Prado
2024-05-29 12:48 ` Andy Shevchenko
2024-05-29 12:56 ` Nícolas F. R. A. Prado
2024-05-23 15:56 ` Mark Brown [this message]
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=171647977136.55224.8875410677372985509.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.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®