From: Vladimir Stankovic <vladimir.stankovic@displaylink.com>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
Petar Kovacevic <petar.kovacevic@displaylink.com>,
Nikola Simic <nikola.simic@displaylink.com>,
Stefan Lugonjic <stefan.lugonjic@displaylink.com>,
Marko Miljkovic <marko.miljkovic@displaylink.com>
Subject: Re: [External] Re: staging: Add MA USB Host driver
Date: Wed, 22 Jan 2020 07:40:59 +0000 [thread overview]
Message-ID: <aba22f24-1124-2203-b9f6-4a5e9274a8a8@displaylink.com> (raw)
In-Reply-To: <20200122070312.GB2068857@kroah.com>
Hi Greg,
Our intention was to follow Linux kernel development process and add our
driver to staging first.
Will resubmit patch with TODO added.
Regards,
Vladimir
On 22.1.20. 08:03, gregkh@linuxfoundation.org wrote:
> On Mon, Jan 20, 2020 at 09:30:43AM +0000, Vladimir Stankovic wrote:
>> MA-USB Host driver provides USB connectivity over an available
>> network, allowing host device to access remote USB devices attached
>> to one or more MA USB devices (accessible via network).
>>
>> This driver has been developed to enable the host to communicate
>> with DislayLink products supporting MA USB protocol (MA USB device,
>> in terms of MA USB Specification).
>>
>> MA-USB protocol used by MA-USB Host driver has been implemented in
>> accordance with MA USB Specification Release 1.0b.
>>
>> This driver depends on the functions provided by DisplayLink's
>> user-space driver.
>>
>> Signed-off-by: Vladimir Stankovic <vladimir.stankovic@displaylink.com>
>
> Why is this being submitted to staging and not to the "real" part of the
> kernel? You need a TODO file that lists what is left to be done to the
> driver to get it merged to the proper place in the kernel tree. Can you
> please resubmit with that file added to the patch?
>
> thanks,
>
> greg k-h
>
next prev parent reply other threads:[~2020-01-22 7:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <VI1PR10MB19659B32E563620B4D63AF1A91320@VI1PR10MB1965.EURPRD10.PROD.OUTLOOK.COM>
[not found] ` <VI1PR10MB1965A077526FE296608D5B1191320@VI1PR10MB1965.EURPRD10.PROD.OUTLOOK.COM>
2020-01-20 9:30 ` Vladimir Stankovic
2020-01-21 8:01 ` Dan Carpenter
2020-01-21 8:13 ` Dan Carpenter
2020-01-22 7:03 ` gregkh
2020-01-22 7:40 ` Vladimir Stankovic [this message]
2020-01-22 7:48 ` [External] " gregkh
2020-01-22 8:16 ` Vladimir Stankovic
2020-01-22 8:49 ` gregkh
2020-01-22 9:07 ` Vladimir Stankovic
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=aba22f24-1124-2203-b9f6-4a5e9274a8a8@displaylink.com \
--to=vladimir.stankovic@displaylink.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marko.miljkovic@displaylink.com \
--cc=nikola.simic@displaylink.com \
--cc=petar.kovacevic@displaylink.com \
--cc=stefan.lugonjic@displaylink.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
all inboxes | Powered by JetHome®