linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Bryant G. Ly" <bryantly@linux.vnet.ibm.com>
To: benh@kernel.crashing.org, mpe@ellerman.id.au,
	gregkh@linuxfoundation.org, arnd@arndb.de
Cc: 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,
	rdunlap@infradead.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,
	"Bryant G. Ly" <bryantly@linux.vnet.ibm.com>
Subject: [PATCH v1 0/1] misc: IBM Virtual Management Channel Driver
Date: Mon, 23 Apr 2018 09:46:51 -0500	[thread overview]
Message-ID: <1524494812-60150-1-git-send-email-bryantly@linux.vnet.ibm.com> (raw)

Steven Royer had previously attempted to upstream this
driver two years ago, but never got the chance to address
the concerns from Greg Kroah-Hartman.

The thread with the initial upstream is:
https://lkml.org/lkml/2016/2/16/918

I have addressed the following:
- Documentation
- Use of dev_dbg instead of pr_dbg
- Change to misc class
- Fixed memory barrier usages
- Addressed styling, checkpatch, renaming of functions
- General fixes to the driver to make it more inline with
  existing upstream drivers.

Bryant G. Ly (1):
  misc: IBM Virtual Management Channel Driver

 Documentation/ioctl/ioctl-number.txt  |    1 +
 Documentation/misc-devices/ibmvmc.txt |  161 +++
 MAINTAINERS                           |    6 +
 arch/powerpc/include/asm/hvcall.h     |    1 +
 drivers/misc/Kconfig                  |    9 +
 drivers/misc/Makefile                 |    1 +
 drivers/misc/ibmvmc.c                 | 2413 +++++++++++++++++++++++++++++++++
 drivers/misc/ibmvmc.h                 |  215 +++
 8 files changed, 2807 insertions(+)
 create mode 100644 Documentation/misc-devices/ibmvmc.txt
 create mode 100644 drivers/misc/ibmvmc.c
 create mode 100644 drivers/misc/ibmvmc.h

-- 
2.7.2

             reply	other threads:[~2018-04-23 14:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-23 14:46 Bryant G. Ly [this message]
2018-04-23 14:46 ` [PATCH v1 1/1] misc: IBM Virtual Management Channel Driver 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
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=1524494812-60150-1-git-send-email-bryantly@linux.vnet.ibm.com \
    --to=bryantly@linux.vnet.ibm.com \
    --cc=adreznec@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=benh@kernel.crashing.org \
    --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=rdunlap@infradead.org \
    --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).