From: Greg KH <gregkh@linuxfoundation.org>
To: Steffen Eiden <seiden@linux.ibm.com>
Cc: linux-s390@vger.kernel.org, Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Janosch Frank <frankja@linux.ibm.com>,
David Hildenbrand <david@redhat.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>,
Shuah Khan <shuah@kernel.org>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v2 1/3] drivers/s390/char: Add Ultravisor io device
Date: Wed, 23 Feb 2022 16:57:57 +0100 [thread overview]
Message-ID: <YhZZhfokG+kWXSSF@kroah.com> (raw)
In-Reply-To: <20220223144830.44039-2-seiden@linux.ibm.com>
On Wed, Feb 23, 2022 at 09:48:28AM -0500, Steffen Eiden wrote:
> --- /dev/null
> +++ b/drivers/s390/char/uvdevice.c
> @@ -0,0 +1,145 @@
> +// SPDX-License-Identifier: GPL-2.0
> +/*
> + * Copyright IBM Corp. 2022
> + * Author(s): Steffen Eiden <seiden@linux.ibm.com>
> + */
> +#define pr_fmt(fmt) KBUILD_MODNAME ": " fmt ".\n"
Nit, this isn't needed as you do not have any pr_* calls that use it :)
thanks,
greg k-h
next prev parent reply other threads:[~2022-02-23 15:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 14:48 [PATCH v2 0/3] s390: Ultravisor device Steffen Eiden
2022-02-23 14:48 ` [PATCH v2 1/3] drivers/s390/char: Add Ultravisor io device Steffen Eiden
2022-02-23 15:57 ` Greg KH [this message]
2022-03-02 10:34 ` Janosch Frank
2022-03-02 10:46 ` Steffen Eiden
2022-03-03 9:53 ` Janosch Frank
2022-03-03 14:17 ` Janosch Frank
2022-02-23 14:48 ` [PATCH v2 2/3] drivers/s390/char: Add Ultravisor attestation to uvdevice Steffen Eiden
2022-03-03 14:44 ` Janosch Frank
2022-02-23 14:48 ` [PATCH v2 3/3] selftests: drivers/s390x: Add uvdevice tests Steffen Eiden
2022-03-04 12:11 ` Janosch Frank
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=YhZZhfokG+kWXSSF@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=seiden@linux.ibm.com \
--cc=shuah@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox