From: Markus Elfring <Markus.Elfring@web.de>
To: Haoxiang Li <make24@iscas.ac.cn>,
linux-hyperv@vger.kernel.org, kernel-janitors@vger.kernel.org,
Andrea Parri <parri.andrea@gmail.com>,
Dexuan Cui <decui@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
"K. Y. Srinivasan" <kys@microsoft.com>,
Michael Kelley <mhklinux@outlook.com>,
Wei Liu <wei.liu@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] drivers: hv: vmbus: Add missing check for dma_set_mask in vmbus_device_register()
Date: Wed, 3 Jul 2024 17:05:14 +0200 [thread overview]
Message-ID: <b0fe50c3-9279-4225-aad5-2869b335fe53@web.de> (raw)
In-Reply-To: <20240703084221.12057-1-make24@iscas.ac.cn>
> child_device_obj->device cannot perform DMA properly if dma_set_mask()
> returns non-zero. …
Can the repetition of another wording suggestion influence the software evolution?
Direct memory access can not be properly performed any more
after a dma_set_mask() call failed.
See also:
https://elixir.bootlin.com/linux/v6.10-rc6/source/kernel/dma/mapping.c#L804
…
> Signed-off-by: Haoxiang Li <make24@iscas.ac.cn>
Under which circumstances will applications of the Developer's Certificate of Origin
be reconsidered any more (after three different names were presented so far)?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.10-rc6#n398
Would you like to append parentheses to another function name in the summary phrase?
Regards,
Markus
next prev parent reply other threads:[~2024-07-03 15:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 8:42 [PATCH v2] drivers: hv: vmbus: Add missing check for dma_set_mask in vmbus_device_register() Haoxiang Li
2024-07-03 15:05 ` Markus Elfring [this message]
2024-07-03 21:16 ` Wei Liu
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=b0fe50c3-9279-4225-aad5-2869b335fe53@web.de \
--to=markus.elfring@web.de \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=make24@iscas.ac.cn \
--cc=mhklinux@outlook.com \
--cc=parri.andrea@gmail.com \
--cc=wei.liu@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