From: Thomas Gleixner <tglx@linutronix.de>
To: Aruna Ramakrishna <aruna.ramakrishna@oracle.com>,
linux-kernel@vger.kernel.org
Cc: x86@kernel.org, dave.hansen@linux.intel.com, mingo@kernel.org,
keith.lucas@oracle.com, aruna.ramakrishna@oracle.com
Subject: Re: [PATCH v3 4/4] selftests/mm: Add new testcases for pkeys
Date: Tue, 07 May 2024 18:56:15 +0200 [thread overview]
Message-ID: <87ttj9pnm8.ffs@tglx> (raw)
In-Reply-To: <875xvprfnm.ffs@tglx>
On Tue, May 07 2024 at 14:05, Thomas Gleixner wrote:
> On Thu, Apr 25 2024 at 18:05, Aruna Ramakrishna wrote:
>> especially with pkey 0 disabled.
>>
>> Signed-off-by: Keith Lucas <keith.lucas@oracle.com>
>> Signed-off-by: Aruna Ramakrishna <aruna.ramakrishna@oracle.com>
Forgot to mention that this Signed-off-by chain is invalid.
next prev parent reply other threads:[~2024-05-07 16:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-25 18:05 [PATCH v3 0/4] x86/pkeys: update PKRU to enable pkey 0 before Aruna Ramakrishna
2024-04-25 18:05 ` [PATCH v3 1/4] x86/pkeys: Signal handling function interface changes to accept PKRU as a parameter Aruna Ramakrishna
2024-05-07 12:16 ` Thomas Gleixner
2024-04-25 18:05 ` [PATCH v3 2/4] x86/pkeys: Add helper functions to update PKRU on sigframe Aruna Ramakrishna
2024-05-07 16:16 ` Thomas Gleixner
2024-05-07 17:15 ` Aruna Ramakrishna
2024-04-25 18:05 ` [PATCH v3 3/4] x86/pkeys: Update PKRU to enable all pkeys before XSAVE Aruna Ramakrishna
2024-05-07 16:47 ` Thomas Gleixner
2024-05-07 17:34 ` Aruna Ramakrishna
2024-05-08 12:52 ` Thomas Gleixner
2024-04-25 18:05 ` [PATCH v3 4/4] selftests/mm: Add new testcases for pkeys Aruna Ramakrishna
2024-05-07 12:05 ` Thomas Gleixner
2024-05-07 16:56 ` Thomas Gleixner [this message]
2024-05-07 18:04 ` Aruna Ramakrishna
2024-05-08 12:55 ` Thomas Gleixner
-- strict thread matches above, loose matches on Subject: below --
2024-04-27 4:07 kernel test robot
2024-05-07 3:17 ` kernel test robot
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=87ttj9pnm8.ffs@tglx \
--to=tglx@linutronix.de \
--cc=aruna.ramakrishna@oracle.com \
--cc=dave.hansen@linux.intel.com \
--cc=keith.lucas@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--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.