From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: mmu: set the contiguous for kernel mappings when appropriate
Date: Tue, 11 Oct 2016 16:10:58 +0100 [thread overview]
Message-ID: <20161011151058.GB25865@remoulade> (raw)
In-Reply-To: <CAKv+Gu_y126PuYhmTq81Psjs6Ss_g2zTYm9asqPDBpc5Uqvh0Q@mail.gmail.com>
On Tue, Oct 11, 2016 at 09:21:14AM +0100, Ard Biesheuvel wrote:
> On 11 October 2016 at 08:44, Mark Rutland <mark.rutland@arm.com> wrote:
> > On Mon, Oct 10, 2016 at 07:12:44PM +0100, Ard Biesheuvel wrote:
> > Not a big deal, but the 'block' part here and elsewhere is now arguably
> > misleading (given 'block' is an architectural term).
> >
> > I haven't come up with a better term, so again, not a big deal. ;)
>
> Indeed. I could simply call it 'allow_cont_mappings' in the context of
> this function, and keep the call below as is.
I'd prefer that the naming is consistent across functions, even if it's left
as-is (and arguably cont makes it sounds like it doesn't cover block mappings).
So unless we find a suitably-equipped thesaurus, as-is is probably fine.
Thanks,
Mark.
next prev parent reply other threads:[~2016-10-11 15:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-10 18:12 [PATCH] arm64: mmu: set the contiguous for kernel mappings when appropriate Ard Biesheuvel
2016-10-11 7:44 ` Mark Rutland
2016-10-11 7:48 ` Mark Rutland
2016-10-11 8:21 ` Ard Biesheuvel
2016-10-11 15:10 ` Mark Rutland [this message]
[not found] ` <CAPvkgC1p5yZLtENYMi6zd5-pPDOYUtMw0Lxvb592u975gc+Zvg@mail.gmail.com>
2016-10-11 9:09 ` Ard Biesheuvel
2016-10-11 11:17 ` Ard Biesheuvel
2016-10-11 12:41 ` Will Deacon
2016-10-11 12:56 ` Ard Biesheuvel
2016-10-11 16:29 ` Will Deacon
2016-10-11 16:38 ` Ard Biesheuvel
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=20161011151058.GB25865@remoulade \
--to=mark.rutland@arm.com \
--cc=linux-arm-kernel@lists.infradead.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 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.