dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: David Lechner <david@lechnology.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2 6/6] drm/tinydrm: Embed the mode in tinydrm_connector
Date: Wed, 10 Jan 2018 09:06:00 +0100	[thread overview]
Message-ID: <20180110080600.GB13066@phenom.ffwll.local> (raw)
In-Reply-To: <ef4f8f5f-11a5-4d0f-419f-809d9242cf52@lechnology.com>

On Tue, Jan 09, 2018 at 09:09:32PM -0600, David Lechner wrote:
> On 01/09/2018 08:05 AM, Noralf Trønnes wrote:
> > 
> > Den 09.01.2018 11.08, skrev Daniel Vetter:
> > > On Mon, Jan 08, 2018 at 07:46:27PM -0600, David Lechner wrote:
> > > > On 01/07/2018 11:44 AM, Noralf Trønnes wrote:
> > > > > Embed the mode in tinydrm_connector instead of doing an devm_ allocation.
> > > > > Remove unnecessary use of ret variable at the end of
> > > > > tinydrm_display_pipe_init().
> > > > > 
> > > > > Signed-off-by: Noralf Trønnes <noralf@tronnes.org>
> > > > > ---
> > > > Reviewed-by: David Lechner <david@lechnology.com>
> > > Since you two work together quit a bit, should we add David as drm-misc
> > > committer?
> > 
> > I would love that. What do you say David?
> > This would mean that you will commit your own work after getting ack/rb.
> 
> Well... I suppose that would be alright.

Please request a freedesktop account for the drm-misc group per

https://www.freedesktop.org/wiki/AccountRequests/

We use a few scripts to handle technicalities and prevent oopsies:

https://01.org/linuxgraphics/gfx-docs/maintainer-tools/dim.html#quickstart

For questions just ping Noralf or any of the other drm-misc
maintainers/committers - #dri-devel on freenode is a good place.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

      reply	other threads:[~2018-01-10  8:06 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-07 17:43 [PATCH v2 0/6] drm/tinydrm: Cleanup Noralf Trønnes
2018-01-07 17:44 ` [PATCH v2 1/6] drm/tinydrm/mi0283qt: Use common include order Noralf Trønnes
2018-01-07 17:44 ` [PATCH v2 2/6] drm/tinydrm/mi0283qt: Remove ili9341.h Noralf Trønnes
2018-01-07 17:44 ` [PATCH v2 3/6] drm/tinydrm/mipi-dbi: Add mipi_dbi_enable_flush() Noralf Trønnes
2018-01-09  1:23   ` David Lechner
2018-01-07 17:44 ` [PATCH v2 4/6] drm/tinydrm/mipi-dbi: Add poweron-reset functions Noralf Trønnes
2018-01-07 20:03   ` Noralf Trønnes
2018-01-09  1:38   ` David Lechner
2018-01-09  1:40     ` David Lechner
2018-01-09 15:01     ` Noralf Trønnes
2018-01-10  3:04       ` David Lechner
2018-01-07 17:44 ` [PATCH v2 5/6] drm/tinydrm/mi0283qt: Let the display pipe handle power Noralf Trønnes
2018-01-09  1:44   ` David Lechner
2018-01-07 17:44 ` [PATCH v2 6/6] drm/tinydrm: Embed the mode in tinydrm_connector Noralf Trønnes
2018-01-09  1:46   ` David Lechner
2018-01-09 10:08     ` Daniel Vetter
2018-01-09 14:05       ` Noralf Trønnes
2018-01-10  3:09         ` David Lechner
2018-01-10  8:06           ` Daniel Vetter [this message]

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=20180110080600.GB13066@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=david@lechnology.com \
    --cc=dri-devel@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox