From: Baolu Lu <baolu.lu@linux.intel.com>
To: 杜敏杰 <duminjie@vivo.com>,
"Thierry Reding" <thierry.reding@gmail.com>,
"Krishna Reddy" <vdumpa@nvidia.com>,
"Joerg Roedel" <joro@8bytes.org>, "Will Deacon" <will@kernel.org>,
"Robin Murphy" <robin.murphy@arm.com>,
"Jonathan Hunter" <jonathanh@nvidia.com>,
"open list:TEGRA IOMMU DRIVERS" <linux-tegra@vger.kernel.org>,
"open list:IOMMU SUBSYSTEM" <iommu@lists.linux.dev>,
"open list" <linux-kernel@vger.kernel.org>
Cc: baolu.lu@linux.intel.com,
"opensource.kernel" <opensource.kernel@vivo.com>,
Thierry Reding <treding@nvidia.com>
Subject: Re: 回复: [PATCH v4] iommu: remove redundant parameter check in tegra_smmu_debugfs_init()
Date: Fri, 14 Jul 2023 10:50:57 +0800 [thread overview]
Message-ID: <ed4200bb-d7e8-b8b5-bfb6-510bebbb8808@linux.intel.com> (raw)
In-Reply-To: <SG2PR06MB5288E9FC9B6EA21E20BB011EAE34A@SG2PR06MB5288.apcprd06.prod.outlook.com>
On 2023/7/14 10:38, 杜敏杰 wrote:
> Hi baolu!
>
> Thanks for your suggestion!
>
> You say:
>> Next time when you send a new version of a patch, please don't forget to add the change log after the tear line. This way, people can know how the patch evolved into this way.
> Do I need to submit a new patch?
Oh no. Just a kind remind. :-)
Best regards,
baolu
next prev parent reply other threads:[~2023-07-14 2:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 7:28 [PATCH v4] iommu: remove redundant parameter check in tegra_smmu_debugfs_init() Minjie Du
2023-07-14 2:31 ` Baolu Lu
[not found] ` <SG2PR06MB5288E9FC9B6EA21E20BB011EAE34A@SG2PR06MB5288.apcprd06.prod.outlook.com>
2023-07-14 2:50 ` Baolu Lu [this message]
2023-07-14 2:57 ` Baolu Lu
[not found] ` <SG2PR06MB5288ED578DB3CE7DA2B25AB5AE34A@SG2PR06MB5288.apcprd06.prod.outlook.com>
2023-07-14 8:41 ` 回复: " Thierry Reding
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=ed4200bb-d7e8-b8b5-bfb6-510bebbb8808@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=duminjie@vivo.com \
--cc=iommu@lists.linux.dev \
--cc=jonathanh@nvidia.com \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=opensource.kernel@vivo.com \
--cc=robin.murphy@arm.com \
--cc=thierry.reding@gmail.com \
--cc=treding@nvidia.com \
--cc=vdumpa@nvidia.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