[PATCH] FBTFT: fbtft-bus: Fix code style problems
Ezequiel Garcia
ezequiel at vanguardiasur.com.ar
Mon Mar 11 21:15:55 UTC 2019
Hi everyone,
Dante: please avoid top-posting. In other words, put your replies in-line,
like I'm gonna do now. See below (and see how discussion goes on other threads).
On Mon, 11 Mar 2019 at 17:34, DANTE JAVIER PAZ <dpaz at unc.edu.ar> wrote:
>
> Hello Sam, thank you very much for your comments,
> As I told Dan (my email did not reach the mailing list) this is my
> first attempt to contribute,
> So I'm learning a lot from your advice and corrections.
>
> I will look for TODO lists to see if there are more useful
> contributions to make, all suggestions are also welcome.
>
> Thanks again for the patience of all of you.
> Best,
> Dante
>
>
> El lun., 11 mar. 2019 a las 13:25, Sam Ravnborg (<sam at ravnborg.org>) escribió:
> >
> > Hi Dante
> >
> > Thanks for the patch.
> > On Sat, Mar 09, 2019 at 06:48:52PM -0300, Dante Paz wrote:
> > > From: Dante Paz <dpaz at unc.edu.ar>
> > >
> > > Style and coding function issues were corrected, by avoiding macro functions with a conflicting coding style.
> > > Signed-off-by: Dante Paz <dpaz at unc.edu.ar>
> >
> > But it raised a few comments.
> >
> > The staging/fbtft is a dumping of a set of drivers that
> > in the end will be migrated to DRM.
> > And there is not much gained trying to do coding style changes to these
> > drivers.
> > So please conmsider finding a drver where this is more relevant.
> >
Sam,
Why is this driver still here? I thought we migrated everyhing to
tinydrm already.
Maybe there's a list of panels still not migrated?
Thanks,
Eze
More information about the dri-devel
mailing list