From: Mark Brown <broonie@kernel.org>
To: Marek Vasut <marex@denx.de>
Cc: Sam Ravnborg <sam@ravnborg.org>, dri-devel@lists.freedesktop.org
Subject: Re: [RFC][PATCH] regulator: rpi-panel: Add regulator/backlight driver for RPi panel
Date: Mon, 3 Aug 2020 20:48:31 +0100 [thread overview]
Message-ID: <20200803194831.GF4502@sirena.org.uk> (raw)
In-Reply-To: <20116f3c-64d7-0f52-b38a-56c62398a5e9@denx.de>
[-- Attachment #1.1: Type: text/plain, Size: 587 bytes --]
On Mon, Aug 03, 2020 at 09:21:25AM +0200, Marek Vasut wrote:
> On 8/1/20 3:16 AM, Mark Brown wrote:
> > I see, so this is the remaining bits. Perhaps the binding might help me
> > see how things fit together - I don't know anything about the system
> > really. It's not doing anything that looks like it should cause the
> > framework too many problems so I'm not overly worried from that point of
> > view but equally well it's obviously not ideal.
> See below:
OK, basically I've got no real objection from a regulator point of view
- it's not ideal but not the end of the world.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-08-03 19:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 21:46 [RFC][PATCH] regulator: rpi-panel: Add regulator/backlight driver for RPi panel Marek Vasut
2020-07-30 15:59 ` Sam Ravnborg
2020-07-30 16:28 ` Marek Vasut
2020-07-30 19:13 ` Mark Brown
2020-07-30 19:37 ` Marek Vasut
2020-08-01 1:16 ` Mark Brown
2020-08-03 7:21 ` Marek Vasut
2020-08-03 19:48 ` Mark Brown [this message]
2020-08-03 22:29 ` Marek Vasut
2020-08-04 14:25 ` Mark Brown
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=20200803194831.GF4502@sirena.org.uk \
--to=broonie@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=marex@denx.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).