From: Shuah Khan <shuah.kh@samsung.com>
To: gregkh@linuxfoundation.org, ly80toro@cip.cs.fau.de,
andy.grover@gmail.com, valentina.manea.m@gmail.com
Cc: Shuah Khan <shuah.kh@samsung.com>,
linux-usb@vger.kernel.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org, shuahkhan@gmail.com
Subject: [PATCH v2 0/3] staging/usbip: add new uapi header usbip.h
Date: Mon, 3 Mar 2014 16:38:42 -0700 [thread overview]
Message-ID: <cover.1393882836.git.shuah.kh@samsung.com> (raw)
usbip userspace has duplicated enum definition to report usbip device
status maintained by the kernel. Adding an usbip uapi header file will
define the kernel - userspace interface for this device status. This
new uapi file is added under usbip/uapi to keep the staging tree code
self-contained. When usbip moves to mainline drivers, this file should
be moved under uapi/linux
usbip kernel and userspace are changed to use this new header file.
Shuah Khan (3):
staging/usbip: add uapi header to export usbip kernel interfaces
staging/usbip: change usbip to include new uapi usbip.h
staging/usbip: change usbip userspace to include new uapi usbip.h
drivers/staging/usbip/uapi/usbip.h | 26 ++++++++++++++++++++
drivers/staging/usbip/usbip_common.h | 19 ++------------
.../staging/usbip/userspace/libsrc/usbip_common.h | 18 +-------------
3 files changed, 29 insertions(+), 34 deletions(-)
create mode 100644 drivers/staging/usbip/uapi/usbip.h
--
1.7.10.4
next reply other threads:[~2014-03-03 23:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 23:38 Shuah Khan [this message]
2014-03-03 23:38 ` [PATCH v2 1/3] staging/usbip: add uapi header to export usbip kernel interfaces Shuah Khan
2014-03-03 23:38 ` [PATCH v2 2/3] staging/usbip: change usbip to include new uapi usbip.h Shuah Khan
2014-03-03 23:38 ` [PATCH v2 3/3] staging/usbip: change usbip userspace " Shuah Khan
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=cover.1393882836.git.shuah.kh@samsung.com \
--to=shuah.kh@samsung.com \
--cc=andy.grover@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=ly80toro@cip.cs.fau.de \
--cc=shuahkhan@gmail.com \
--cc=valentina.manea.m@gmail.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
Powered by JetHome