From: Philipp Zabel <p.zabel@pengutronix.de>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Steffen Trumtrar <s.trumtrar@pengutronix.de>,
dri-devel@lists.freedesktop.org, kernel@pengutronix.de
Subject: Re: [PATCH 1/3] drm/panel: Add display_timing support
Date: Tue, 24 Mar 2015 12:52:44 +0100 [thread overview]
Message-ID: <1427197964.3180.20.camel@pengutronix.de> (raw)
In-Reply-To: <20150324113430.GN18115@ulmo.nvidia.com>
Am Dienstag, den 24.03.2015, 12:34 +0100 schrieb Thierry Reding:
[...]
> > > Would you prefer
> > > struct display_timing *(*get_timing)(struct drm_panel *panel);
> > > ?
> >
> > I'd like to resend this. Please let me know if you want me to change
> > this function prototype.
>
> I have no objections to keeping the current prototype. It's something we
> can always fixup if we want to. Also keeping the symmetry with min/max
> values for hactive and vactive is okay in my opinion.
>
> Were there any other remaining points? If not I'll just apply this as
> is.
No, I'm happy if you apply this as is.
thanks
Philipp
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-03-24 11:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 17:32 [PATCH 1/3] drm/panel: Add display_timing support Philipp Zabel
2014-12-11 17:32 ` [PATCH 2/3] drm/panel: Add display_timing support to simple panel driver Philipp Zabel
2014-12-11 17:32 ` [PATCH 3/3] drm/panel: Add display_timing entry for the HannStar HSD070PWW1 panel Philipp Zabel
2015-02-03 13:30 ` [PATCH 1/3] drm/panel: Add display_timing support Thierry Reding
2015-02-03 16:56 ` Philipp Zabel
2015-02-23 14:04 ` Philipp Zabel
2015-02-26 13:51 ` Boris Brezillon
2015-02-26 18:33 ` Philipp Zabel
2015-03-03 11:49 ` Philipp Zabel
2015-03-24 11:34 ` Thierry Reding
2015-03-24 11:52 ` Philipp Zabel [this message]
2015-03-24 12:40 ` Thierry Reding
2015-03-24 16:36 ` Philipp Zabel
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=1427197964.3180.20.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel@pengutronix.de \
--cc=s.trumtrar@pengutronix.de \
--cc=thierry.reding@gmail.com \
/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