From: Greg KH <gregkh@linuxfoundation.org>
To: Shuah Khan <shuah.kh@samsung.com>
Cc: ly80toro@cip.cs.fau.de, andy.grover@gmail.com,
valentina.manea.m@gmail.com, linux-usb@vger.kernel.org,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
shuahkhan@gmail.com
Subject: Re: [PATCH 1/3] staging/usbip: add uapi header to export usbip kernel interfaces
Date: Fri, 28 Feb 2014 14:15:58 -0800 [thread overview]
Message-ID: <20140228221558.GA17000@kroah.com> (raw)
In-Reply-To: <10c9784313c5bafc6410b95cb3b569d5925eeaaa.1393542201.git.shuah.kh@samsung.com>
On Thu, Feb 27, 2014 at 05:27:25PM -0700, Shuah Khan wrote:
> 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.
>
> Signed-off-by: Shuah Khan <shuah.kh@samsung.com>
> ---
> include/uapi/linux/Kbuild | 1 +
> include/uapi/linux/usbip.h | 26 ++++++++++++++++++++++++++
> 2 files changed, 27 insertions(+)
> create mode 100644 include/uapi/linux/usbip.h
Staging code should be self-contained within drivers/staging/
Now I know that a bunch of people are now working on this codebase, and
hopefully it will finally get moved out of staging someday soon, but
until then, I can't add this file in this location, sorry.
Look at how the drivers/staging/android code handles the uapi files, you
should try doing that instead.
thanks,
greg k-h
next prev parent reply other threads:[~2014-02-28 22:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 0:27 [PATCH 0/3] staging/usbip: add new uapi header usbip.h Shuah Khan
2014-02-28 0:27 ` [PATCH 1/3] staging/usbip: add uapi header to export usbip kernel interfaces Shuah Khan
2014-02-28 22:15 ` Greg KH [this message]
2014-02-28 22:45 ` Shuah Khan
2014-02-28 0:27 ` [PATCH 2/3] staging/usbip: change usbip to include new uapi usbip.h Shuah Khan
2014-02-28 0:27 ` [PATCH 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=20140228221558.GA17000@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andy.grover@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=ly80toro@cip.cs.fau.de \
--cc=shuah.kh@samsung.com \
--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