[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180715100345.GA17618@kroah.com>
Date: Sun, 15 Jul 2018 12:03:45 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Dmitry Torokhov <dtor@...omium.org>
Cc: devel@...verdev.osuosl.org, toddpoynor@...il.com,
frankhu@...omium.org, jnjoseph@...gle.com,
lkml <linux-kernel@...r.kernel.org>,
Simon Que <sque@...omium.org>, rspringer@...gle.com,
Guenter Roeck <groeck@...omium.org>, toddpoynor@...gle.com
Subject: Re: [PATCH 11/18] staging: gasket: always allow root open for write
On Sun, Jul 15, 2018 at 12:53:09PM +0300, Dmitry Torokhov wrote:
> > I can't wait for people to just realize this whole "new" subsystem can
> > be replaced with UIO, but that's a topic for a different thread...
>
> Yes, that is true and that is why I am not sure why we are going
> through all this staging exercise.
>
> As far as I understand we'd still need to have quite a bit of kernel
> code so that we can safely program DMA controller (it does not look
> like uio_dmem_genirq.c is sufficient as is for gasket needs), but that
> should be solvable.
I agree, it should be solvable, and much smaller and simpler than this
whole large chunk of "subsystem+driver" code. But I'm not the one
having to do this work, and it provides a bunch of easy cleanups for
people looking to get into kernel development, so I don't mind :)
But the "maintainers" should keep this in mind, as it is, this code is
_not_ acceptable for the main kernel tree because of the UIO framework
already present.
thanks,
greg k-h
Powered by blists - more mailing lists