On Fri, Jan 25, 2019 at 09:12:49AM -0800, Olof Johansson wrote: > On Fri, Jan 25, 2019 at 8:06 AM Greg Kroah-Hartman > <gre...@linuxfoundation.org> wrote: > > > > On Fri, Jan 25, 2019 at 07:33:23AM -0800, Olof Johansson wrote: > > > On Thu, Jan 24, 2019 at 11:37 PM Greg Kroah-Hartman > > > > As for what directory the code should live in, I suggested "misc" as > > > > there was no other universal location, and I hate to see new subsystems > > > > be created with only one driver, as that's pretty sad. But it's just a > > > > name/location, I have no dog in the fight, so I really don't care where > > > > it ends up in the tree, just as long as it gets merged somewhere :) > > > > > > I'm usually one to push back against new subsystems too, especially > > > when I see a framework proposal with just one driver. In this case, > > > given that we all know more vendors will come along, I think it makes > > > sense to take the discussion and establish structure now. This should > > > give some clarity to those who are out there that we haven't seen yet, > > > and give them a chance to prepare for things such as the low-level > > > userspace pieces mentioned above. > > > > > > So I think setting this up now is the right thing to do, we know there > > > will be more material here and having a common aggregation of it makes > > > sense. > > > > Ok, how about: > > drivers/deep_thought/ > > > > as a first proposal. > > > > Let the bikeshedding begin! :) > > My original proposal upthread was driver/accel. I'm not sure whether > Dave and/or anyone else wants to participate to start though, I hope > they will at least join in once things are heading in the direction > they want. > > I'll post patches with the proposed moves and documentation of > expectations shortly, hopefully to collect acks.
Patches all look good to me, I can merge them through my char-misc tree once we get the acks from the relevant driver maintainers. thanks, greg k-h