From: Francesco Valla <francesco@valla.it>
To: Daniel Pereira <danielmaraboo@gmail.com>
Cc: andersson@kernel.org, mathieu.poirier@linaro.org,
linux-remoteproc@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC v2 08/11] Documentation: remoteproc: expand virtio support section
Date: Fri, 6 Nov 2026 22:29:45 +0100 [thread overview]
Message-ID: <au5GNZqGkN-0Qn84@bywater> (raw)
In-Reply-To: <CAMAsx6dogk20pTtpGaD_Ci2fam01UuUEe3KXDTH7UVjwRBRqnw@mail.gmail.com>
Hi Daniel,
On Tue, Nov 03, 2026 at 11:15:23AM -0300, Daniel Pereira wrote:
> On Sun, Nov 01, 2026 08:28 PM, Francesco Valla <francesco@valla.it> wrote:
> >
> Hi Francesco,
>
> I only have a few language nits:
>
> > +supplied by the remote processor should be marked as dynamically allocable,
>
> "allocable" -> "allocatable".
>
> > +try to allocate it using dma_alloc_coherent(), which will resort to allocate it
>
> "resort to" takes a gerund: "which will resort to allocating it".
>
> > +either from the first ``restricted-dma-pool`` region associated to the virtio
>
> "associated to" -> "associated with". The same wording appears several
> times in the patch (e.g. "associated to the virtio device's parent"), so
> please fix all of them.
>
All the nits will be addresed in v3.
As you may have imagined (also considering that my email address' domain
gives me away...) english is not my primary language, so any correction
is more than welcome.
> Thanks,
> Daniel
>
Thank you!
Regards,
Francesco
next prev parent reply other threads:[~2026-11-06 21:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-01 23:26 [PATCH RFC v2 00/11] remoteproc: add support for any virtio device Francesco Valla
2026-11-01 23:26 ` [PATCH RFC v2 01/11] remoteproc: virtio: cleanup rproc_add_virtio_dev error path Francesco Valla
2026-11-01 23:26 ` [PATCH RFC v2 02/11] remoteproc: virtio: replace commas with semicolons Francesco Valla
2026-11-01 23:26 ` [PATCH RFC v2 03/11] remoteproc: virtio: support dynamic number of vrings Francesco Valla
2026-11-01 23:26 ` [PATCH RFC v2 04/11] remoteproc: report VIRTIO_F_VERSION_1 for non-rproc-specific vdevs Francesco Valla
2026-11-01 23:26 ` [PATCH RFC v2 05/11] remoteproc: virtio: report VIRTIO_F_ACCESS_PLATFORM when required Francesco Valla
2026-11-01 23:26 ` [PATCH RFC v2 06/11] dt-bindings: remoteproc: add remoteproc-virtio Francesco Valla
2026-11-01 23:26 ` [PATCH RFC v2 07/11] remoteproc: assign fwnode during vdev registration Francesco Valla
2026-11-01 23:26 ` [PATCH RFC v2 08/11] Documentation: remoteproc: expand virtio support section Francesco Valla
2026-11-03 14:15 ` Daniel Pereira
2026-11-06 21:29 ` Francesco Valla [this message]
2026-11-01 23:26 ` [PATCH RFC v2 09/11] remoteproc: imx_rproc: always use non-blocking mailboxes Francesco Valla
2026-11-01 23:26 ` [PATCH RFC v2 10/11] dt-bindings: remoteproc: imx-rproc: support virtio Francesco Valla
2026-11-01 23:26 ` [PATCH RFC v2 11/11] PoC: arm64: dts: imx93-11x11-frdm: add multiple vdevs Francesco Valla
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=au5GNZqGkN-0Qn84@bywater \
--to=francesco@valla.it \
--cc=andersson@kernel.org \
--cc=danielmaraboo@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@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®