From: patchwork-bot+linux-remoteproc@kernel.org
To: Alexander Lobakin <alobakin@pm.me>
Cc: linux-remoteproc@vger.kernel.org
Subject: Re: [PATCH virtio] virtio: virtio_console: fix DMA memory allocation for rproc serial
Date: Mon, 28 Dec 2020 18:54:43 +0000 [thread overview]
Message-ID: <160918168375.4261.7525417768126390145.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <AOKowLclCbOCKxyiJ71WeNyuAAj2q8EUtxrXbyky5E@cp7-web-042.plabs.ch>
Hello:
This patch was applied to andersson/remoteproc.git (refs/heads/for-next):
On Wed, 04 Nov 2020 15:31:36 +0000 you wrote:
> Since commit 086d08725d34 ("remoteproc: create vdev subdevice with
> specific dma memory pool"), every remoteproc has a DMA subdevice
> ("remoteprocX#vdevYbuffer") for each virtio device, which inherits
> DMA capabilities from the corresponding platform device. This allowed
> to associate different DMA pools with each vdev, and required from
> virtio drivers to perform DMA operations with the parent device
> (vdev->dev.parent) instead of grandparent (vdev->dev.parent->parent).
>
> [...]
Here is the summary with links:
- [virtio] virtio: virtio_console: fix DMA memory allocation for rproc serial
https://git.kernel.org/andersson/remoteproc/c/9d516aa82b7d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2020-12-28 18:55 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 15:31 [PATCH virtio] virtio: virtio_console: fix DMA memory allocation for rproc serial Alexander Lobakin
2020-11-04 18:21 ` Mathieu Poirier
2020-11-05 3:10 ` Jason Wang
2020-11-05 3:10 ` Jason Wang
2020-11-05 12:22 ` Alexander Lobakin
2020-11-09 6:04 ` Jason Wang
2020-11-09 6:04 ` Jason Wang
2020-11-16 9:19 ` Christoph Hellwig
2020-11-16 9:19 ` Christoph Hellwig
2020-11-16 9:51 ` Michael S. Tsirkin
2020-11-16 9:51 ` Michael S. Tsirkin
2020-11-16 16:27 ` Christoph Hellwig
2020-11-16 16:27 ` Christoph Hellwig
2020-11-16 16:43 ` Alexander Lobakin
2020-11-16 10:46 ` Arnaud POULIQUEN
2020-11-16 10:46 ` Arnaud POULIQUEN
2020-11-16 16:28 ` Christoph Hellwig
2020-11-16 16:28 ` Christoph Hellwig
2020-11-16 16:39 ` Christoph Hellwig
2020-11-16 16:39 ` Christoph Hellwig
2020-11-17 14:00 ` Arnaud POULIQUEN
2020-11-17 14:00 ` Arnaud POULIQUEN
2020-11-17 14:02 ` Christoph Hellwig
2020-11-17 14:02 ` Christoph Hellwig
2020-11-18 10:16 ` Michael S. Tsirkin
2020-11-18 10:16 ` Michael S. Tsirkin
2020-11-16 12:25 ` Michael S. Tsirkin
2020-11-16 12:25 ` Michael S. Tsirkin
2020-11-16 13:07 ` Alexander Lobakin
2020-11-16 13:12 ` Michael S. Tsirkin
2020-11-16 13:12 ` Michael S. Tsirkin
2020-11-16 16:30 ` Christoph Hellwig
2020-11-16 16:30 ` Christoph Hellwig
2020-12-28 18:54 ` patchwork-bot+linux-remoteproc [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=160918168375.4261.7525417768126390145.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-remoteproc@kernel.org \
--cc=alobakin@pm.me \
--cc=linux-remoteproc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.