All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: devel@driverdev.osuosl.org, DANTE JAVIER PAZ <dpaz@unc.edu.ar>,
	linux-fbdev@vger.kernel.org, nishadkamdar@gmail.com,
	leobras.c@gmail.com, Greg KH <gregkh@linuxfoundation.org>,
	Dante Paz <dante.paz@gmail.com>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	renatoys08@gmail.com
Subject: Re: [PATCH] FBTFT: fbtft-bus: Fix code style problems
Date: Mon, 11 Mar 2019 21:43:43 +0000	[thread overview]
Message-ID: <CAAEAJfCNhtGwpZWMDv2nQJcK7nsY6onKLd0DhNFcSJNN+8ZLag@mail.gmail.com> (raw)
In-Reply-To: <20190311214004.GA9670@ravnborg.org>

On Mon, 11 Mar 2019 at 18:40, Sam Ravnborg <sam@ravnborg.org> wrote:
>
> Hi Eze
> >
> > Why is this driver still here? I thought we migrated everyhing to
> > tinydrm already.
> Some have been ported, some are waiting for a user to do the port.
> If you looks at tinydrm you will see:
> ili9225.c  ili9341.c
>
> And we also have under panel:
> panel-ilitek-ili9881c.c
> panel-ilitek-ili9322.c
>
> But in staging there are more panels than just these.
>
> So we have not yet ported all.
> And there is today no list of what is missing.
>

Right.

Perhaps the TODO file on fbtft should be updated stating clearly that
we don't care about cleaning this one.
This is important given staging is used for Outreachy and other
introductory programs.

We can also add some big fat warning message (in case there isn't one
already) asking users of staging/fbtft to help porting/testing the
port to tinydrm.

Thanks,
Eze

WARNING: multiple messages have this Message-ID (diff)
From: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: devel@driverdev.osuosl.org, DANTE JAVIER PAZ <dpaz@unc.edu.ar>,
	linux-fbdev@vger.kernel.org, nishadkamdar@gmail.com,
	leobras.c@gmail.com, Greg KH <gregkh@linuxfoundation.org>,
	Dante Paz <dante.paz@gmail.com>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	renatoys08@gmail.com
Subject: Re: [PATCH] FBTFT: fbtft-bus: Fix code style problems
Date: Mon, 11 Mar 2019 18:43:43 -0300	[thread overview]
Message-ID: <CAAEAJfCNhtGwpZWMDv2nQJcK7nsY6onKLd0DhNFcSJNN+8ZLag@mail.gmail.com> (raw)
In-Reply-To: <20190311214004.GA9670@ravnborg.org>

On Mon, 11 Mar 2019 at 18:40, Sam Ravnborg <sam@ravnborg.org> wrote:
>
> Hi Eze
> >
> > Why is this driver still here? I thought we migrated everyhing to
> > tinydrm already.
> Some have been ported, some are waiting for a user to do the port.
> If you looks at tinydrm you will see:
> ili9225.c  ili9341.c
>
> And we also have under panel:
> panel-ilitek-ili9881c.c
> panel-ilitek-ili9322.c
>
> But in staging there are more panels than just these.
>
> So we have not yet ported all.
> And there is today no list of what is missing.
>

Right.

Perhaps the TODO file on fbtft should be updated stating clearly that
we don't care about cleaning this one.
This is important given staging is used for Outreachy and other
introductory programs.

We can also add some big fat warning message (in case there isn't one
already) asking users of staging/fbtft to help porting/testing the
port to tinydrm.

Thanks,
Eze
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2019-03-11 21:43 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-09 21:48 [PATCH] FBTFT: fbtft-bus: Fix code style problems Dante Paz
2019-03-09 21:48 ` Dante Paz
2019-03-11  8:11 ` Dan Carpenter
2019-03-11  8:11   ` Dan Carpenter
2019-03-11  8:18 ` Dan Carpenter
2019-03-11  8:18   ` Dan Carpenter
2019-03-11 14:06   ` DANTE JAVIER PAZ
2019-03-11 16:25 ` Sam Ravnborg
2019-03-11 16:25   ` Sam Ravnborg
2019-03-11 20:32   ` DANTE JAVIER PAZ
2019-03-11 20:32     ` DANTE JAVIER PAZ
2019-03-11 21:15     ` Ezequiel Garcia
2019-03-11 21:15       ` Ezequiel Garcia
2019-03-11 21:40       ` Sam Ravnborg
2019-03-11 21:40         ` Sam Ravnborg
2019-03-11 21:43         ` Ezequiel Garcia [this message]
2019-03-11 21:43           ` Ezequiel Garcia
2019-03-11 21:42     ` Sam Ravnborg
2019-03-11 21:42       ` Sam Ravnborg

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=CAAEAJfCNhtGwpZWMDv2nQJcK7nsY6onKLd0DhNFcSJNN+8ZLag@mail.gmail.com \
    --to=ezequiel@vanguardiasur.com.ar \
    --cc=dante.paz@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=dpaz@unc.edu.ar \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=leobras.c@gmail.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=nishadkamdar@gmail.com \
    --cc=renatoys08@gmail.com \
    --cc=sam@ravnborg.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.