From: Markus Elfring <Markus.Elfring@web.de>
To: XianLiang Huang <huangxianliang@lanxincomputing.com>,
iommu@lists.linux.dev, linux-riscv@lists.infradead.org
Cc: LKML <linux-kernel@vger.kernel.org>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Alexandre Ghiti" <alex@ghiti.fr>, "Jörg Rödel" <joro@8bytes.org>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
"Robin Murphy" <robin.murphy@arm.com>,
"Tomasz Jeznach" <tjeznach@rivosinc.com>,
"Will Deacon" <will@kernel.org>
Subject: Re: [v4] iommu/riscv: prevent NULL deref in iova_to_phys
Date: Wed, 20 Aug 2025 13:30:16 +0200 [thread overview]
Message-ID: <aed0e72a-3c98-4027-8676-b8f469d857f5@web.de> (raw)
In-Reply-To: <20250820111643.19464-1-huangxianliang@lanxincomputing.com>
>> Does it trigger undesirable communication difficulties?
> No, and I agree that both subject and summary phrase can be improved
I suggest to take another look for the better distinction of mentioned key words.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.17-rc2#n638
Regards,
Markus
next prev parent reply other threads:[~2025-08-20 11:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-20 7:22 [PATCH v4] " XianLiang Huang
2025-08-20 8:25 ` Markus Elfring
2025-08-20 9:21 ` XianLiang Huang
2025-08-20 10:40 ` [v4] " Markus Elfring
2025-08-20 11:16 ` XianLiang Huang
2025-08-20 11:30 ` Markus Elfring [this message]
2025-08-22 2:36 ` XianLiang Huang
2025-08-22 6:52 ` [PATCH v4] " Joerg Roedel
2025-10-09 1:07 ` patchwork-bot+linux-riscv
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=aed0e72a-3c98-4027-8676-b8f469d857f5@web.de \
--to=markus.elfring@web.de \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=huangxianliang@lanxincomputing.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robin.murphy@arm.com \
--cc=tjeznach@rivosinc.com \
--cc=will@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®