From: Peng Hao <peng.hao2@zte.com.cn>
To: gregkh@linuxfoundation.org, arnd@arndb.de, andy.shevchenko@gmail.com
Cc: linux-kernel@vger.kernel.org, Peng Hao <peng.hao2@zte.com.cn>
Subject: [PATCH RESEND V5 1/3] misc/pvpanic: return 0 for empty body register function
Date: Thu, 20 Dec 2018 13:14:46 +0800 [thread overview]
Message-ID: <1545282888-38059-1-git-send-email-peng.hao2@zte.com.cn> (raw)
Return 0 for empty body register function normally.
Signed-off-by: Peng Hao <peng.hao2@zte.com.cn>
---
v4 --> v5 : resolve kbuild issue: handle all typo "drvier/driver"
in funtion name.
v3 --> v4 : use pcim* function instead of pci* function.
handle typo "drvier/driver" in funtion name.
v2 --> v3 : resolve kbuild issue : a uninitialized variable in some path.
v2 --> v1 : resolve kbuild issue : arch=sh don't support pci, adjust
CONFIG_PCI macro.
v1 : QEMU community requires additional PCI devices to simulate PVPANIC devices
so that some architectures can not occupy precious less than 4G of memory
space.
drivers/misc/pvpanic.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/misc/pvpanic.c b/drivers/misc/pvpanic.c
index 3150dc2..f84ed30 100644
--- a/drivers/misc/pvpanic.c
+++ b/drivers/misc/pvpanic.c
@@ -125,7 +125,7 @@ static void pvpanic_unregister_acpi_driver(void)
#else
static int pvpanic_register_acpi_driver(void)
{
- return -ENODEV;
+ return 0;
}
static void pvpanic_unregister_acpi_driver(void) {}
--
1.8.3.1
next reply other threads:[~2018-12-20 4:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-20 5:14 Peng Hao [this message]
2018-12-20 5:14 ` [PATCH RESEND V5 2/3] misc/pvpanic : add pci interface for pvpanic Peng Hao
2019-01-03 20:05 ` Andy Shevchenko
2018-12-20 5:14 ` [PATCH RESEND V5 3/3] misc/pvpanic : add pci dependency in Kconfig Peng Hao
2019-01-18 15:32 ` [PATCH RESEND V5 1/3] misc/pvpanic: return 0 for empty body register function Greg KH
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=1545282888-38059-1-git-send-email-peng.hao2@zte.com.cn \
--to=peng.hao2@zte.com.cn \
--cc=andy.shevchenko@gmail.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).