From: Randy Dunlap <rdunlap@infradead.org>
To: Mihai Carabas <mihai.carabas@oracle.com>, linux-kernel@vger.kernel.org
Cc: gregkh@linuxfoundation.org, arnd@arndb.de,
andriy.shevchenko@linux.intel.com, bobo.shaobowang@huawei.com
Subject: Re: [PATCH 1/2] misc/pvpanic: split-up generic and platform dependent code
Date: Wed, 3 Feb 2021 09:13:39 -0800 [thread overview]
Message-ID: <9080b512-33a8-e9f9-7c4c-bc2572ab7e5c@infradead.org> (raw)
In-Reply-To: <1612363439-26656-2-git-send-email-mihai.carabas@oracle.com>
On 2/3/21 6:43 AM, Mihai Carabas wrote:
> diff --git a/drivers/misc/pvpanic/Kconfig b/drivers/misc/pvpanic/Kconfig
> new file mode 100644
> index 00000000..12bb017
> --- /dev/null
> +++ b/drivers/misc/pvpanic/Kconfig
> @@ -0,0 +1,14 @@
> +config PVPANIC
> + bool "pvpanic device support"
> + depends on PVPANIC_MMIO
> + help
> + This option enable generic code for pvpanic device driver logic.
> +
> +config PVPANIC_MMIO
> + tristate "pvpanic mmio device support"
MMIO
Also capitalize PCI in the other patch in the similar location.
> + depends on HAS_IOMEM && (ACPI || OF)
> + select PVPANIC
> + help
> + This driver provides support for the pvpanic device. pvpanic is
> + a paravirtualized device provided by QEMU; it lets a virtual machine
> + (guest) communicate panic events to the host.
thanks.
--
~Randy
next prev parent reply other threads:[~2021-02-03 17:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-03 14:43 [PATCH] add support for pci in the pvpanic driver Mihai Carabas
2021-02-03 14:43 ` [PATCH 1/2] misc/pvpanic: split-up generic and platform dependent code Mihai Carabas
2021-02-03 15:44 ` Greg KH
2021-02-03 17:13 ` Randy Dunlap [this message]
2021-02-03 19:57 ` kernel test robot
2021-02-03 23:18 ` kernel test robot
2021-02-03 14:43 ` [PATCH 2/2] misc/pvpanic: add pci driver Mihai Carabas
2021-02-03 15:41 ` Greg KH
2021-02-03 15:44 ` 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=9080b512-33a8-e9f9-7c4c-bc2572ab7e5c@infradead.org \
--to=rdunlap@infradead.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=bobo.shaobowang@huawei.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mihai.carabas@oracle.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).