[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <98df2373-6f19-df36-c78c-e0384ddb8730@displaylink.com>
Date: Wed, 22 Jan 2020 08:16:09 +0000
From: Vladimir Stankovic <vladimir.stankovic@...playlink.com>
To: "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"devel@...verdev.osuosl.org" <devel@...verdev.osuosl.org>,
Petar Kovacevic <petar.kovacevic@...playlink.com>,
Nikola Simic <nikola.simic@...playlink.com>,
Stefan Lugonjic <stefan.lugonjic@...playlink.com>,
Marko Miljkovic <marko.miljkovic@...playlink.com>
Subject: Re: [External] Re: staging: Add MA USB Host driver
Hi Greg,
It was section 2.5 of the kernel development process, "staging trees".
In particular, statement "where many sub-directories for drivers or
filesystems that are on their way to being added to the kernel tree
live" caught our attention.
Now, by reading it once again, I see that the rest of the section is in
line with your comment.
We'll address all comments received so far, and resubmit patch onto
appropriate repository. With that being said, is USB subsystem tree
(drivers/usb within usb.git repo) correct one? Please, advise.
Thanks.
Regards,
Vladimir.
On 22.1.20. 08:48, gregkh@...uxfoundation.org wrote:
> On Wed, Jan 22, 2020 at 07:40:59AM +0000, Vladimir Stankovic wrote:
>> Hi Greg,
>>
>> Our intention was to follow Linux kernel development process and add our
>> driver to staging first.
>
> That's not the "normal" development process at all, where did you read
> that?
>
> staging is only for code that needs lots of work, and almost always
> merging a driver through staging takes _more_ work from the submitter
> than it does to submit it through the "normal" subsystem.
>
> So if you want to do more work, hey, by all means, send it here :)
>
> thanks,
>
> greg k-h
>
Powered by blists - more mailing lists