From: Borislav Petkov <bp@alien8.de>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-s390@vger.kernel.org,
Dave Hansen <dave.hansen@linux.intel.com>,
Vasily Gorbik <gor@linux.ibm.com>,
linuxppc-dev@lists.ozlabs.org,
Peter Zijlstra <peterz@infradead.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
x86@kernel.org, Heiko Carstens <heiko.carstens@de.ibm.com>,
lkml <linux-kernel@vger.kernel.org>,
Christian Borntraeger <borntraeger@de.ibm.com>,
iommu@lists.linux-foundation.org, Ingo Molnar <mingo@redhat.com>,
Paul Mackerras <paulus@samba.org>,
Tom Lendacky <thomas.lendacky@amd.com>,
Andy Lutomirski <luto@kernel.org>,
Michael Ellerman <mpe@ellerman.id.au>,
Thomas Gleixner <tglx@linutronix.de>,
Robin Murphy <robin.murphy@arm.com>
Subject: Re: [PATCH -v2] treewide: Rename "unencrypted" to "decrypted"
Date: Thu, 19 Mar 2020 11:28:34 +0100 [thread overview]
Message-ID: <20200319102834.GC13073@zn.tnic> (raw)
In-Reply-To: <20200319102011.GA3617@lst.de>
On Thu, Mar 19, 2020 at 11:20:11AM +0100, Christoph Hellwig wrote:
> I thought we agreed that decrypted is absolutely the wrong term.
I don't think we did. At least I don't know where we did that.
> So NAK - if you want to change things it needs to go the other way.
We are already using "decrypted" everywhere in arch/x86/. Changing that
would be a *lot* more churn.
And it is just a term, for chrissakes, to denote memory which is not
encrypted. And it would make our lifes easier if we had only *two* terms
instead of three or more. Especially if the concept we denote with this
is a binary one: encrypted memory and *not* encrypted memory.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Borislav Petkov <bp@alien8.de>
To: Christoph Hellwig <hch@lst.de>
Cc: lkml <linux-kernel@vger.kernel.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Michael Ellerman <mpe@ellerman.id.au>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
x86@kernel.org, Dave Hansen <dave.hansen@linux.intel.com>,
Andy Lutomirski <luto@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Robin Murphy <robin.murphy@arm.com>,
linuxppc-dev@lists.ozlabs.org, linux-s390@vger.kernel.org,
iommu@lists.linux-foundation.org,
Tom Lendacky <thomas.lendacky@amd.com>
Subject: Re: [PATCH -v2] treewide: Rename "unencrypted" to "decrypted"
Date: Thu, 19 Mar 2020 11:28:34 +0100 [thread overview]
Message-ID: <20200319102834.GC13073@zn.tnic> (raw)
In-Reply-To: <20200319102011.GA3617@lst.de>
On Thu, Mar 19, 2020 at 11:20:11AM +0100, Christoph Hellwig wrote:
> I thought we agreed that decrypted is absolutely the wrong term.
I don't think we did. At least I don't know where we did that.
> So NAK - if you want to change things it needs to go the other way.
We are already using "decrypted" everywhere in arch/x86/. Changing that
would be a *lot* more churn.
And it is just a term, for chrissakes, to denote memory which is not
encrypted. And it would make our lifes easier if we had only *two* terms
instead of three or more. Especially if the concept we denote with this
is a binary one: encrypted memory and *not* encrypted memory.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
WARNING: multiple messages have this Message-ID (diff)
From: Borislav Petkov <bp@alien8.de>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-s390@vger.kernel.org,
Dave Hansen <dave.hansen@linux.intel.com>,
Vasily Gorbik <gor@linux.ibm.com>,
linuxppc-dev@lists.ozlabs.org,
Peter Zijlstra <peterz@infradead.org>,
x86@kernel.org, Heiko Carstens <heiko.carstens@de.ibm.com>,
lkml <linux-kernel@vger.kernel.org>,
Christian Borntraeger <borntraeger@de.ibm.com>,
iommu@lists.linux-foundation.org, Ingo Molnar <mingo@redhat.com>,
Paul Mackerras <paulus@samba.org>,
Tom Lendacky <thomas.lendacky@amd.com>,
Andy Lutomirski <luto@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Robin Murphy <robin.murphy@arm.com>,
Marek Szyprowski <m.szyprowski@samsung.com>
Subject: Re: [PATCH -v2] treewide: Rename "unencrypted" to "decrypted"
Date: Thu, 19 Mar 2020 11:28:34 +0100 [thread overview]
Message-ID: <20200319102834.GC13073@zn.tnic> (raw)
In-Reply-To: <20200319102011.GA3617@lst.de>
On Thu, Mar 19, 2020 at 11:20:11AM +0100, Christoph Hellwig wrote:
> I thought we agreed that decrypted is absolutely the wrong term.
I don't think we did. At least I don't know where we did that.
> So NAK - if you want to change things it needs to go the other way.
We are already using "decrypted" everywhere in arch/x86/. Changing that
would be a *lot* more churn.
And it is just a term, for chrissakes, to denote memory which is not
encrypted. And it would make our lifes easier if we had only *two* terms
instead of three or more. Especially if the concept we denote with this
is a binary one: encrypted memory and *not* encrypted memory.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2020-03-19 10:28 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-17 11:18 [PATCH] treewide: Rename "unencrypted" to "decrypted" Borislav Petkov
2020-03-17 11:18 ` Borislav Petkov
2020-03-17 11:18 ` Borislav Petkov
2020-03-17 11:18 ` Borislav Petkov
2020-03-17 20:35 ` Dave Hansen
2020-03-17 20:35 ` Dave Hansen
2020-03-17 20:35 ` Dave Hansen
2020-03-17 21:06 ` Borislav Petkov
2020-03-17 21:06 ` Borislav Petkov
2020-03-17 21:06 ` Borislav Petkov
2020-03-17 21:24 ` Dave Hansen
2020-03-17 21:24 ` Dave Hansen
2020-03-17 21:24 ` Dave Hansen
2020-03-17 21:31 ` Borislav Petkov
2020-03-17 21:31 ` Borislav Petkov
2020-03-17 21:31 ` Borislav Petkov
2020-03-17 21:34 ` Joe Perches
2020-03-17 21:34 ` Joe Perches
2020-03-17 21:34 ` Joe Perches
2020-03-17 22:01 ` Thomas Gleixner
2020-03-17 22:01 ` Thomas Gleixner
2020-03-17 22:01 ` Thomas Gleixner
2020-03-17 22:01 ` Thomas Gleixner
2020-03-17 23:16 ` kbuild test robot
2020-03-17 23:16 ` kbuild test robot
2020-03-17 23:16 ` kbuild test robot
2020-03-17 23:16 ` kbuild test robot
2020-03-17 23:51 ` kbuild test robot
2020-03-17 23:51 ` kbuild test robot
2020-03-17 23:51 ` kbuild test robot
2020-03-17 23:51 ` kbuild test robot
2020-03-19 10:16 ` [PATCH -v2] " Borislav Petkov
2020-03-19 10:16 ` Borislav Petkov
2020-03-19 10:16 ` Borislav Petkov
2020-03-19 10:20 ` Christoph Hellwig
2020-03-19 10:20 ` Christoph Hellwig
2020-03-19 10:20 ` Christoph Hellwig
2020-03-19 10:28 ` Borislav Petkov [this message]
2020-03-19 10:28 ` Borislav Petkov
2020-03-19 10:28 ` Borislav Petkov
2020-03-19 11:06 ` Robin Murphy
2020-03-19 11:06 ` Robin Murphy
2020-03-19 11:06 ` Robin Murphy
2020-03-19 11:20 ` Borislav Petkov
2020-03-19 11:20 ` Borislav Petkov
2020-03-19 11:20 ` Borislav Petkov
2020-03-19 17:25 ` Thomas Gleixner
2020-03-19 17:25 ` Thomas Gleixner
2020-03-19 17:25 ` Thomas Gleixner
2020-03-19 17:42 ` Borislav Petkov
2020-03-19 17:42 ` Borislav Petkov
2020-03-19 17:42 ` Borislav Petkov
2020-03-19 23:53 ` Thomas Gleixner
2020-03-19 23:53 ` Thomas Gleixner
2020-03-19 23:53 ` Thomas Gleixner
2020-03-19 21:59 ` Michal Suchánek
2020-03-19 21:59 ` Michal Suchánek
2020-03-19 21:59 ` Michal Suchánek
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=20200319102834.GC13073@zn.tnic \
--to=bp@alien8.de \
--cc=benh@kernel.crashing.org \
--cc=borntraeger@de.ibm.com \
--cc=dave.hansen@linux.intel.com \
--cc=gor@linux.ibm.com \
--cc=hch@lst.de \
--cc=heiko.carstens@de.ibm.com \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=robin.murphy@arm.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=x86@kernel.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.