public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Steffen Eiden <seiden@linux.ibm.com>
To: linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org
Cc: Ingo Franzki <ifranzki@linux.ibm.com>,
	Harald Freudenberger <freude@linux.ibm.com>,
	Christoph Schlameuss <schlameuss@linux.ibm.com>,
	Janosch Frank <frankja@linux.ibm.com>,
	Claudio Imbrenda <imbrenda@linux.ibm.com>
Subject: Re: [PATCH v3 0/6] s390/uv: Retrieve Secrets Ultravisor Call support
Date: Tue, 15 Oct 2024 13:37:53 +0200	[thread overview]
Message-ID: <5295d507-a82a-409a-817e-c15847ebe850@linux.ibm.com> (raw)
In-Reply-To: <20241015112859.3069210-1-seiden@linux.ibm.com>

On 10/15/24 1:28 PM, Steffen Eiden wrote:

[..]
> Since v3:
> 	* rename BIT_UVC_CMD_RETR_SECRETS to BIT_UVC_CMD_RETR_SECRET
> 	* Streamline list_secrets()
> 	* Fix documentation styling issues
> 	* Simplify conditional in find_secret()
> 	* Add r-b from Christoph
accidentally added a 'since v3'. These are the changes compared to v2 (yet again)
[..]

      parent reply	other threads:[~2024-10-15 11:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-15 11:28 [PATCH v3 0/6] s390/uv: Retrieve Secrets Ultravisor Call support Steffen Eiden
2024-10-15 11:28 ` [PATCH v3 1/6] s390/boot/uv.c: Use a constant for more-data rc Steffen Eiden
2024-10-15 11:28 ` [PATCH v3 2/6] s390/uv: Retrieve UV secrets support Steffen Eiden
2024-10-15 11:28 ` [PATCH v3 3/6] s390/uvdevice: Add Retrieve Secret IOCTL Steffen Eiden
2024-10-15 11:28 ` [PATCH v3 4/6] s390/uvdevice: Increase indent in IOCTL definitions Steffen Eiden
2024-10-15 11:28 ` [PATCH v3 5/6] s390/uvdevice: Add List Secrets Ext IOCTL Steffen Eiden
2024-10-15 12:01   ` Heiko Carstens
2024-10-16  9:06     ` Steffen Eiden
2024-10-16  3:13   ` kernel test robot
2024-10-15 11:28 ` [PATCH v3 6/6] s390/uv: Retrieve UV secrets sysfs support Steffen Eiden
2024-10-15 11:37 ` Steffen Eiden [this message]

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=5295d507-a82a-409a-817e-c15847ebe850@linux.ibm.com \
    --to=seiden@linux.ibm.com \
    --cc=frankja@linux.ibm.com \
    --cc=freude@linux.ibm.com \
    --cc=ifranzki@linux.ibm.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=schlameuss@linux.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox