From: Randy Dunlap <rdunlap@infradead.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "Bryant G. Ly" <bryantly@linux.vnet.ibm.com>,
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
Subject: Re: [PATCH v1 1/1] misc: IBM Virtual Management Channel Driver
Date: Tue, 24 Apr 2018 08:21:20 -0700 [thread overview]
Message-ID: <f8f39907-82c8-cf73-bcb2-3601c56c7c09@infradead.org> (raw)
In-Reply-To: <20180424142918.GA2459@kroah.com>
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 <bryantly@linux.vnet.ibm.com>
>>>>> Reviewed-by: Steven Royer <seroyer@linux.vnet.ibm.com>
>>>>> Reviewed-by: Adam Reznechek <adreznec@linux.vnet.ibm.com>
>>>>> Tested-by: Taylor Jakobson <tjakobs@us.ibm.com>
>>>>> Tested-by: Brad Warrum <bwarrum@us.ibm.com>
>>>>> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>>>>> Cc: Arnd Bergmann <arnd@arndb.de>
>>>>> Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
>>>>> Cc: Michael Ellerman <mpe@ellerman.id.au>
>>>>> ---
>>>>> 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
next prev parent reply other threads:[~2018-04-24 15:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-23 14:46 [PATCH v1 0/1] misc: IBM Virtual Management Channel Driver Bryant G. Ly
2018-04-23 14:46 ` [PATCH v1 1/1] " Bryant G. Ly
2018-04-23 18:38 ` Randy Dunlap
2018-04-23 19:53 ` Greg KH
2018-04-23 21:06 ` Bryant G. Ly
2018-04-23 21:17 ` Randy Dunlap
2018-04-24 14:29 ` Greg KH
2018-04-24 15:21 ` Randy Dunlap [this message]
2018-04-25 8:29 ` Linus Walleij
2018-04-25 12:00 ` kbuild test robot
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=f8f39907-82c8-cf73-bcb2-3601c56c7c09@infradead.org \
--to=rdunlap@infradead.org \
--cc=adreznec@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=benh@kernel.crashing.org \
--cc=bryantly@linux.vnet.ibm.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=fbarrat@linux.vnet.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=linus.walleij@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.org \
--cc=mpe@ellerman.id.au \
--cc=mrochs@linux.vnet.ibm.com \
--cc=msuchanek@suse.de \
--cc=pombredanne@nexb.com \
--cc=seroyer@linux.vnet.ibm.com \
--cc=tlfalcon@linux.vnet.ibm.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).