From: Greg KH <gregkh@linuxfoundation.org>
To: David Kershner <david.kershner@unisys.com>
Cc: corbet@lwn.net, tglx@linutronix.de, mingo@redhat.com,
hpa@zytor.com, erik.arfvidson@unisys.com,
timothy.sell@unisys.com, hofrat@osadl.org, dzickus@redhat.com,
jes.sorensen@redhat.com, alexander.curtin@unisys.com,
janani.rvchndrn@gmail.com, sudipm.mukherjee@gmail.com,
prarit@redhat.com, david.binder@unisys.com, nhorman@redhat.com,
dan.j.williams@intel.com, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org,
driverdev-devel@linuxdriverproject.org,
sparmaintainer@unisys.com
Subject: Re: [PATCH 4/5] staging: unisys: visorbus: Have visorbus use include/linux/visorbus
Date: Tue, 17 May 2016 06:52:07 -0700 [thread overview]
Message-ID: <20160517135207.GD18227@kroah.com> (raw)
In-Reply-To: <1463470081-24223-5-git-send-email-david.kershner@unisys.com>
On Tue, May 17, 2016 at 03:28:00AM -0400, David Kershner wrote:
> Since we have now moved the include directories over to
> include/linux/visorbus this patch makes all of visorbus
> use the new include folders.
>
> Signed-off-by: David Kershner <david.kershner@unisys.com>
> ---
> drivers/staging/unisys/visorbus/controlvmchannel.h | 2 +-
> drivers/staging/unisys/visorbus/periodic_work.c | 3 +--
> drivers/staging/unisys/visorbus/vbuschannel.h | 3 ++-
> drivers/staging/unisys/visorbus/visorbus_main.c | 8 ++++----
> drivers/staging/unisys/visorbus/visorchannel.c | 4 ++--
> drivers/staging/unisys/visorbus/visorchipset.c | 10 +++++-----
> drivers/staging/unisys/visorbus/vmcallinterface.h | 5 ++---
> 7 files changed, 17 insertions(+), 18 deletions(-)
Does that mean the build was broken before you made this patch? Not
allowed, sorry :(
next prev parent reply other threads:[~2016-05-17 13:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-17 7:27 [PATCH 0/5] add bus driver for Unisys s-Par paravirtualized devices to arch/x86 David Kershner
2016-05-17 7:27 ` [PATCH 1/5] staging: unisys: Move vbushelper.h to visorbus directory David Kershner
2016-05-17 7:27 ` [PATCH 2/5] include: linux: visorbus: Add visorbus to include/linux directory David Kershner
2016-05-17 7:27 ` [PATCH 3/5] Documentation: Move visorbus documentation from staging to Documentation/ David Kershner
2016-05-17 13:50 ` Greg KH
2016-05-17 7:28 ` [PATCH 4/5] staging: unisys: visorbus: Have visorbus use include/linux/visorbus David Kershner
2016-05-17 13:52 ` Greg KH [this message]
2016-05-17 7:28 ` [PATCH 5/5] arch: x86: add visorbus directory to arch/x86 David Kershner
2016-05-17 13:51 ` [PATCH 0/5] add bus driver for Unisys s-Par paravirtualized devices " Greg KH
2016-05-17 14:01 ` Jes Sorensen
2016-05-17 14:27 ` Greg KH
2016-05-17 23:49 ` Jes Sorensen
2016-05-18 0:03 ` Greg KH
2016-05-18 16:03 ` Jes Sorensen
2016-05-18 17:26 ` 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=20160517135207.GD18227@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alexander.curtin@unisys.com \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=david.binder@unisys.com \
--cc=david.kershner@unisys.com \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=dzickus@redhat.com \
--cc=erik.arfvidson@unisys.com \
--cc=hofrat@osadl.org \
--cc=hpa@zytor.com \
--cc=janani.rvchndrn@gmail.com \
--cc=jes.sorensen@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nhorman@redhat.com \
--cc=prarit@redhat.com \
--cc=sparmaintainer@unisys.com \
--cc=sudipm.mukherjee@gmail.com \
--cc=tglx@linutronix.de \
--cc=timothy.sell@unisys.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