All of lore.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: Anshuman Khandual <anshuman.khandual@arm.com>,
	linux-arm-kernel@lists.infradead.org
Cc: catalin.marinas@arm.com, kernel-team@android.com,
	Will Deacon <will@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64/mm: Drop redundant BUG_ON(!pgtable_alloc)
Date: Fri, 18 Nov 2022 19:40:38 +0000	[thread overview]
Message-ID: <166878064180.1782449.376709845468504621.b4-ty@kernel.org> (raw)
In-Reply-To: <20221118053102.500216-1-anshuman.khandual@arm.com>

On Fri, 18 Nov 2022 11:01:02 +0530, Anshuman Khandual wrote:
> __create_pgd_mapping_locked() expects a page allocator used while mapping a
> virtual range. This page allocator function propagates down the call chain,
> while building intermediate levels in the page table. Passed page allocator
> is a necessary ingredient required to build the page table but its presence
> can be asserted just once in the very beginning rather than in all the down
> stream functions. This consolidates BUG_ON(!pgtable_alloc) checks just in a
> single place i.e __create_pgd_mapping_locked().
> 
> [...]

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

[1/1] arm64/mm: Drop redundant BUG_ON(!pgtable_alloc)
      https://git.kernel.org/arm64/c/9ed2b4616d4e

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

WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will@kernel.org>
To: Anshuman Khandual <anshuman.khandual@arm.com>,
	linux-arm-kernel@lists.infradead.org
Cc: catalin.marinas@arm.com, kernel-team@android.com,
	Will Deacon <will@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64/mm: Drop redundant BUG_ON(!pgtable_alloc)
Date: Fri, 18 Nov 2022 19:40:38 +0000	[thread overview]
Message-ID: <166878064180.1782449.376709845468504621.b4-ty@kernel.org> (raw)
In-Reply-To: <20221118053102.500216-1-anshuman.khandual@arm.com>

On Fri, 18 Nov 2022 11:01:02 +0530, Anshuman Khandual wrote:
> __create_pgd_mapping_locked() expects a page allocator used while mapping a
> virtual range. This page allocator function propagates down the call chain,
> while building intermediate levels in the page table. Passed page allocator
> is a necessary ingredient required to build the page table but its presence
> can be asserted just once in the very beginning rather than in all the down
> stream functions. This consolidates BUG_ON(!pgtable_alloc) checks just in a
> single place i.e __create_pgd_mapping_locked().
> 
> [...]

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

[1/1] arm64/mm: Drop redundant BUG_ON(!pgtable_alloc)
      https://git.kernel.org/arm64/c/9ed2b4616d4e

Cheers,
-- 
Will

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

  parent reply	other threads:[~2022-11-18 19:42 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-18  5:31 [PATCH] arm64/mm: Drop redundant BUG_ON(!pgtable_alloc) Anshuman Khandual
2022-11-18  5:31 ` Anshuman Khandual
2022-11-18 11:10 ` Mark Rutland
2022-11-18 11:10   ` Mark Rutland
2022-11-18 19:40 ` Will Deacon [this message]
2022-11-18 19:40   ` Will Deacon
2022-11-20 16:16 ` Nathan Chancellor
2022-11-20 16:16   ` Nathan Chancellor
2022-11-21  5:30   ` Anshuman Khandual
2022-11-21  5:30     ` Anshuman Khandual
2022-11-21 12:27     ` Mark Rutland
2022-11-21 12:27       ` Mark Rutland
2022-11-21 12:51       ` Will Deacon
2022-11-21 12:51         ` Will Deacon
2022-11-21 13:56       ` Robin Murphy
2022-11-21 13:56         ` Robin Murphy
2022-11-22  3:13         ` Anshuman Khandual
2022-11-22  3:13           ` Anshuman Khandual
2022-11-22 14:12           ` Biju Das
2022-11-22 14:12             ` Biju Das
2022-11-22 19:08           ` Robin Murphy
2022-11-22 19:08             ` Robin Murphy
  -- strict thread matches above, loose matches on Subject: below --
2022-11-21 15:47 Naresh Kamboju
2022-11-21 18:03 ` Will Deacon
2022-11-21 18:03   ` 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=166878064180.1782449.376709845468504621.b4-ty@kernel.org \
    --to=will@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=anshuman.khandual@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=kernel-team@android.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@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.