All of lore.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: Miaohe Lin <linmiaohe@huawei.com>, catalin.marinas@arm.com
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>,
	vincenzo.frascino@arm.com, mark.rutland@arm.com,
	andreyknvl@google.com, linux-kernel@vger.kernel.org,
	akpm@linux-foundation.org, pcc@google.com,
	linux-arm-kernel@lists.infradead.org, peterx@redhat.com,
	elver@google.com
Subject: Re: [PATCH] mm/arm64: Correct obsolete comment in do_page_fault()
Date: Fri,  5 Feb 2021 18:52:51 +0000	[thread overview]
Message-ID: <161255062810.1453555.15259323279738372740.b4-ty@kernel.org> (raw)
In-Reply-To: <20210205090919.63382-1-linmiaohe@huawei.com>

On Fri, 5 Feb 2021 04:09:19 -0500, Miaohe Lin wrote:
> commit d8ed45c5dcd4 ("mmap locking API: use coccinelle to convert mmap_sem
> rwsem call sites") has convertd down_read_trylock() to mmap_read_trylock().
> But it forgot to update the relevant comment.

Applied to arm64 (for-next/cosmetic), thanks!

[1/1] mm/arm64: Correct obsolete comment in do_page_fault()
      https://git.kernel.org/arm64/c/abd4737f67d7

Cheers,
-- 
Will

https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev

WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will@kernel.org>
To: Miaohe Lin <linmiaohe@huawei.com>, catalin.marinas@arm.com
Cc: mark.rutland@arm.com, elver@google.com, pcc@google.com,
	kernel-team@android.com, linux-kernel@vger.kernel.org,
	peterx@redhat.com, andreyknvl@google.com,
	akpm@linux-foundation.org, vincenzo.frascino@arm.com,
	Will Deacon <will@kernel.org>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] mm/arm64: Correct obsolete comment in do_page_fault()
Date: Fri,  5 Feb 2021 18:52:51 +0000	[thread overview]
Message-ID: <161255062810.1453555.15259323279738372740.b4-ty@kernel.org> (raw)
In-Reply-To: <20210205090919.63382-1-linmiaohe@huawei.com>

On Fri, 5 Feb 2021 04:09:19 -0500, Miaohe Lin wrote:
> commit d8ed45c5dcd4 ("mmap locking API: use coccinelle to convert mmap_sem
> rwsem call sites") has convertd down_read_trylock() to mmap_read_trylock().
> But it forgot to update the relevant comment.

Applied to arm64 (for-next/cosmetic), thanks!

[1/1] mm/arm64: Correct obsolete comment in do_page_fault()
      https://git.kernel.org/arm64/c/abd4737f67d7

Cheers,
-- 
Will

https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-02-05 18:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-05  9:09 [PATCH] mm/arm64: Correct obsolete comment in do_page_fault() Miaohe Lin
2021-02-05  9:09 ` Miaohe Lin
2021-02-05 18:52 ` Will Deacon [this message]
2021-02-05 18:52   ` Will Deacon

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=161255062810.1453555.15259323279738372740.b4-ty@kernel.org \
    --to=will@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=andreyknvl@google.com \
    --cc=catalin.marinas@arm.com \
    --cc=elver@google.com \
    --cc=kernel-team@android.com \
    --cc=linmiaohe@huawei.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=pcc@google.com \
    --cc=peterx@redhat.com \
    --cc=vincenzo.frascino@arm.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.