From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from bombadil.infradead.org (bombadil.infradead.org [IPv6:2607:7c80:54:e::133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 40Vn9M6z5jzF1RV for ; Wed, 25 Apr 2018 01:21:27 +1000 (AEST) Subject: Re: [PATCH v1 1/1] misc: IBM Virtual Management Channel Driver To: Greg KH Cc: "Bryant G. Ly" , benh@kernel.crashing.org, mpe@ellerman.id.au, arnd@arndb.de, corbet@lwn.net, seroyer@linux.vnet.ibm.com, mrochs@linux.vnet.ibm.com, adreznec@linux.vnet.ibm.com, fbarrat@linux.vnet.ibm.com, davem@davemloft.net, linus.walleij@linaro.org, akpm@linux-foundation.org, mikey@neuling.org, pombredanne@nexb.com, tlfalcon@linux.vnet.ibm.com, msuchanek@suse.de, linux-doc@vger.kernel.org, linuxppc-dev@lists.ozlabs.org References: <1524494812-60150-1-git-send-email-bryantly@linux.vnet.ibm.com> <1524494812-60150-2-git-send-email-bryantly@linux.vnet.ibm.com> <20180423195310.GA10693@kroah.com> <4142fd3b-05eb-d934-bcd3-f8f564e24fa7@infradead.org> <20180424142918.GA2459@kroah.com> From: Randy Dunlap Message-ID: Date: Tue, 24 Apr 2018 08:21:20 -0700 MIME-Version: 1.0 In-Reply-To: <20180424142918.GA2459@kroah.com> Content-Type: text/plain; charset=utf-8 List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On 04/24/2018 07:29 AM, Greg KH wrote: > On Mon, Apr 23, 2018 at 02:17:28PM -0700, Randy Dunlap wrote: >> On 04/23/18 12:53, Greg KH wrote: >>> On Mon, Apr 23, 2018 at 11:38:18AM -0700, Randy Dunlap wrote: >>>> On 04/23/18 07:46, Bryant G. Ly wrote: >>>>> This driver is a logical device which provides an >>>>> interface between the hypervisor and a management >>>>> partition. >>>>> >>>>> This driver is to be used for the POWER Virtual >>>>> Management Channel Virtual Adapter on the PowerVM >>>>> platform. It provides both request/response and >>>>> async message support through the /dev/ibmvmc node. >>>>> >>>>> Signed-off-by: Bryant G. Ly >>>>> Reviewed-by: Steven Royer >>>>> Reviewed-by: Adam Reznechek >>>>> Tested-by: Taylor Jakobson >>>>> Tested-by: Brad Warrum >>>>> Cc: Greg Kroah-Hartman >>>>> Cc: Arnd Bergmann >>>>> Cc: Benjamin Herrenschmidt >>>>> Cc: Michael Ellerman >>>>> --- >>>>> Documentation/ioctl/ioctl-number.txt | 1 + >>>>> Documentation/misc-devices/ibmvmc.txt | 161 +++ >>>>> MAINTAINERS | 6 + >>>>> arch/powerpc/include/asm/hvcall.h | 1 + >>>>> drivers/misc/Kconfig | 14 + >>>>> drivers/misc/Makefile | 1 + >>>>> drivers/misc/ibmvmc.c | 2415 +++++++++++++++++++++++++++++++++ >>>>> drivers/misc/ibmvmc.h | 209 +++ >>>>> 8 files changed, 2808 insertions(+) >>>>> create mode 100644 Documentation/misc-devices/ibmvmc.txt >>>>> create mode 100644 drivers/misc/ibmvmc.c >>>>> create mode 100644 drivers/misc/ibmvmc.h >>>> >>>>> diff --git a/Documentation/misc-devices/ibmvmc.txt b/Documentation/misc-devices/ibmvmc.txt >>>>> new file mode 100644 >>>>> index 0000000..bae1064 >>>>> --- /dev/null >>>>> +++ b/Documentation/misc-devices/ibmvmc.txt >>> >>> Aren't we doing new documentation in .rst format instead of .txt? >> >> I am not aware that .rst format is a *requirement* for new documentation. >> >> ?? > > Why wouldn't you create new documentation in that format? Just saves > the step of having to change it again in the future. Not everything needs to be in that format. If a document contains graphics or lots of tables, then sure, use RST. Do you do kernel Documentation builds yourself? Do you know how slow they are? -- ~Randy