public inbox for linux-mm@kvack.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Christoph Hellwig <hch@lst.de>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org
Subject: Re: [PATCH] mm: remove mmu_notifier_get
Date: Wed, 16 Sep 2020 12:53:39 -0300	[thread overview]
Message-ID: <20200916155339.GB8409@ziepe.ca> (raw)
In-Reply-To: <20200916112724.2174759-1-hch@lst.de>

On Wed, Sep 16, 2020 at 01:27:24PM +0200, Christoph Hellwig wrote:
> Remove the unused mmu_notifier_get inline function.
> 
> Signed-off-by: Christoph Hellwig <hch@lst.de>
>  include/linux/mmu_notifier.h | 10 ----------
>  1 file changed, 10 deletions(-)
> 
> diff --git a/include/linux/mmu_notifier.h b/include/linux/mmu_notifier.h
> index b8200782dedeb9..acd1cc41f25d81 100644
> +++ b/include/linux/mmu_notifier.h
> @@ -279,16 +279,6 @@ static inline int mm_has_notifiers(struct mm_struct *mm)
>  
>  struct mmu_notifier *mmu_notifier_get_locked(const struct mmu_notifier_ops *ops,
>  					     struct mm_struct *mm);
> -static inline struct mmu_notifier *
> -mmu_notifier_get(const struct mmu_notifier_ops *ops, struct mm_struct *mm)
> -{
> -	struct mmu_notifier *ret;
> -
> -	mmap_write_lock(mm);
> -	ret = mmu_notifier_get_locked(ops, mm);
> -	mmap_write_unlock(mm);
> -	return ret;
> -}
>  void mmu_notifier_put(struct mmu_notifier *subscription);
>  void mmu_notifier_synchronize(void);

Looks like I missed this from 

Fixes: f25a546e6529 ("RDMA/odp: Use mmu_interval_notifier_insert()")

Though, I have a vauge recollection that some SVA IOMMU patches posted
wanted to use this too? They can bring it back if it makes sense

Looks like David is right about the comment, but aside from that:

Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>

v2 should go through Andrew's tree

Thanks,
Jason  


      parent reply	other threads:[~2020-09-16 15:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-16 11:27 [PATCH] mm: remove mmu_notifier_get Christoph Hellwig
2020-09-16 12:33 ` David Hildenbrand
2020-09-16 15:53 ` Jason Gunthorpe [this message]

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=20200916155339.GB8409@ziepe.ca \
    --to=jgg@ziepe.ca \
    --cc=akpm@linux-foundation.org \
    --cc=hch@lst.de \
    --cc=linux-mm@kvack.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