[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZLrb2Xq/ZgDgVPNf@ziepe.ca>
Date: Fri, 21 Jul 2023 16:26:17 -0300
From: Jason Gunthorpe <jgg@...pe.ca>
To: Alistair Popple <apopple@...dia.com>
Cc: akpm@...ux-foundation.org, ajd@...ux.ibm.com,
catalin.marinas@....com, fbarrat@...ux.ibm.com,
iommu@...ts.linux.dev, jhubbard@...dia.com, kevin.tian@...el.com,
kvm@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
linuxppc-dev@...ts.ozlabs.org, mpe@...erman.id.au,
nicolinc@...dia.com, npiggin@...il.com, robin.murphy@....com,
seanjc@...gle.com, will@...nel.org, x86@...nel.org,
zhi.wang.linux@...il.com, sj@...nel.org
Subject: Re: [PATCH v3 2/5] mmu_notifiers: Fixup comment in
mmu_interval_read_begin()
On Thu, Jul 20, 2023 at 06:39:24PM +1000, Alistair Popple wrote:
> The comment in mmu_interval_read_begin() refers to a function that
> doesn't exist and uses the wrong call-back name. The op for mmu
> interval notifiers is mmu_interval_notifier_ops->invalidate() so fix
> the comment up to reflect that.
>
> Signed-off-by: Alistair Popple <apopple@...dia.com>
> ---
> mm/mmu_notifier.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Reviewed-by: Jason Gunthorpe <jgg@...dia.com>
Jason
Powered by blists - more mailing lists