From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Yuanchu Xie <yuanchu@google.com>
Cc: Wei Liu <liuwe@microsoft.com>,
Rob Bradford <rbradford@rivosinc.com>,
Theodore Ts'o <tytso@mit.edu>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
virtualization@lists.linux.dev, dev@lists.cloudhypervisor.org
Subject: Re: [PATCH v3 1/2] virt: pvmemcontrol: control guest physical memory properties
Date: Wed, 16 Oct 2024 21:44:33 +0200 [thread overview]
Message-ID: <2024101657-motion-lunacy-dc6d@gregkh> (raw)
In-Reply-To: <20241016193947.48534-1-yuanchu@google.com>
On Wed, Oct 16, 2024 at 12:39:46PM -0700, Yuanchu Xie wrote:
> + dev_info(dev->device,
> + "pvmemcontrol_vmm_info.ret_errno = %u\n"
> + "pvmemcontrol_vmm_info.ret_code = %u\n"
> + "pvmemcontrol_vmm_info.major_version = %llu\n"
> + "pvmemcontrol_vmm_info.minor_version = %llu\n"
> + "pvmemcontrol_vmm_info.page_size = %llu\n",
> + dev->pvmemcontrol_vmm_info.ret_errno,
> + dev->pvmemcontrol_vmm_info.ret_code,
> + dev->pvmemcontrol_vmm_info.arg0,
> + dev->pvmemcontrol_vmm_info.arg1,
> + dev->pvmemcontrol_vmm_info.ret_value);
When a driver works properly, it is quiet. Please do not spam the
kernel log when your driver properly binds to the device like this,
that's just not ok at all.
thanks,
greg k-h
prev parent reply other threads:[~2024-10-16 19:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 19:39 [PATCH v3 1/2] virt: pvmemcontrol: control guest physical memory properties Yuanchu Xie
2024-10-16 19:39 ` [PATCH v3 2/2] virt: pvmemcontrol: add Yuanchu and Pasha as maintainers Yuanchu Xie
2024-10-16 19:42 ` [PATCH v3 1/2] virt: pvmemcontrol: control guest physical memory properties Greg Kroah-Hartman
2024-10-16 19:44 ` Greg Kroah-Hartman [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=2024101657-motion-lunacy-dc6d@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dev@lists.cloudhypervisor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liuwe@microsoft.com \
--cc=pasha.tatashin@soleen.com \
--cc=rbradford@rivosinc.com \
--cc=tytso@mit.edu \
--cc=virtualization@lists.linux.dev \
--cc=yuanchu@google.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;
as well as URLs for NNTP newsgroup(s).