All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Dave Hansen <dave.hansen@intel.com>
Cc: "Schofield, Alison" <alison.schofield@intel.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	Heiko Carstens <heiko.carstens@de.ibm.com>,
	Paul Mackerras <paulus@samba.org>, Christoph Hellwig <hch@lst.de>,
	linux-s390@vger.kernel.org, Michael Ellerman <mpe@ellerman.id.au>,
	x86@kernel.org, Christian Borntraeger <borntraeger@de.ibm.com>,
	Ingo Molnar <mingo@redhat.com>,
	Tom Lendacky <thomas.lendacky@amd.com>,
	Vasily Gorbik <gor@linux.ibm.com>,
	"Shutemov, Kirill" <kirill.shutemov@intel.com>,
	Andy Lutomirski <luto@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Robin Murphy <robin.murphy@arm.com>,
	lkml <linux-kernel@vger.kernel.org>,
	iommu@lists.linux-foundation.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] treewide: Rename "unencrypted" to "decrypted"
Date: Tue, 17 Mar 2020 22:31:14 +0100	[thread overview]
Message-ID: <20200317213100.GH15609@zn.tnic> (raw)
In-Reply-To: <f3e520c6-f455-9c82-abfc-d014ca63eeb5@intel.com>

On Tue, Mar 17, 2020 at 02:24:59PM -0700, Dave Hansen wrote:
> No, there are just two states.  I just think the "!encrypted" case
> should not be called "decrypted".

Yeah, we suck at naming - news at 11! :-)

I believe we even considered things like "encrypted" vs "clear" but
that sucked too. ;-\

In any case, that ship has sailed now and having two as differently as
possible looking words to denote the two "states" should be good enough
for our purposes...

Oh well.

-- 
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: Dave Hansen <dave.hansen@intel.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
	"Schofield, Alison" <alison.schofield@intel.com>,
	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>,
	Christoph Hellwig <hch@lst.de>,
	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>,
	"Shutemov, Kirill" <kirill.shutemov@intel.com>
Subject: Re: [PATCH] treewide: Rename "unencrypted" to "decrypted"
Date: Tue, 17 Mar 2020 22:31:14 +0100	[thread overview]
Message-ID: <20200317213100.GH15609@zn.tnic> (raw)
In-Reply-To: <f3e520c6-f455-9c82-abfc-d014ca63eeb5@intel.com>

On Tue, Mar 17, 2020 at 02:24:59PM -0700, Dave Hansen wrote:
> No, there are just two states.  I just think the "!encrypted" case
> should not be called "decrypted".

Yeah, we suck at naming - news at 11! :-)

I believe we even considered things like "encrypted" vs "clear" but
that sucked too. ;-\

In any case, that ship has sailed now and having two as differently as
possible looking words to denote the two "states" should be good enough
for our purposes...

Oh well.

-- 
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: Dave Hansen <dave.hansen@intel.com>
Cc: "Schofield, Alison" <alison.schofield@intel.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	Heiko Carstens <heiko.carstens@de.ibm.com>,
	Paul Mackerras <paulus@samba.org>, Christoph Hellwig <hch@lst.de>,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	linux-s390@vger.kernel.org, x86@kernel.org,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	Ingo Molnar <mingo@redhat.com>,
	Tom Lendacky <thomas.lendacky@amd.com>,
	Vasily Gorbik <gor@linux.ibm.com>,
	"Shutemov, Kirill" <kirill.shutemov@intel.com>,
	Andy Lutomirski <luto@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Robin Murphy <robin.murphy@arm.com>,
	lkml <linux-kernel@vger.kernel.org>,
	iommu@lists.linux-foundation.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] treewide: Rename "unencrypted" to "decrypted"
Date: Tue, 17 Mar 2020 22:31:14 +0100	[thread overview]
Message-ID: <20200317213100.GH15609@zn.tnic> (raw)
In-Reply-To: <f3e520c6-f455-9c82-abfc-d014ca63eeb5@intel.com>

On Tue, Mar 17, 2020 at 02:24:59PM -0700, Dave Hansen wrote:
> No, there are just two states.  I just think the "!encrypted" case
> should not be called "decrypted".

Yeah, we suck at naming - news at 11! :-)

I believe we even considered things like "encrypted" vs "clear" but
that sucked too. ;-\

In any case, that ship has sailed now and having two as differently as
possible looking words to denote the two "states" should be good enough
for our purposes...

Oh well.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

  reply	other threads:[~2020-03-17 21:31 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 [this message]
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
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=20200317213100.GH15609@zn.tnic \
    --to=bp@alien8.de \
    --cc=alison.schofield@intel.com \
    --cc=benh@kernel.crashing.org \
    --cc=borntraeger@de.ibm.com \
    --cc=dave.hansen@intel.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=kirill.shutemov@intel.com \
    --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.