From: Maxime Ripard <maxime@cerno.tech>
To: Mark Brown <broonie@kernel.org>
Cc: Stefan Wahren <stefan.wahren@i2se.com>,
David Airlie <airlied@linux.ie>,
Liam Girdwood <lgirdwood@gmail.com>,
dri-devel@lists.freedesktop.org,
Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
Subject: Re: [PATCH RFC] drm/vc4: hdmi: Avoid ASoC error messages on startup
Date: Fri, 15 Jan 2021 19:14:37 +0100 [thread overview]
Message-ID: <20210115181437.uqlkrbapv6ydswuy@gilmour> (raw)
In-Reply-To: <20210113114223.GB4641@sirena.org.uk>
[-- Attachment #1.1: Type: text/plain, Size: 625 bytes --]
Hi,
On Wed, Jan 13, 2021 at 11:42:23AM +0000, Mark Brown wrote:
> On Wed, Jan 13, 2021 at 10:19:57AM +0100, Maxime Ripard wrote:
>
> > I'd like to get Mark's opinion before merging though
>
> I'm not sure what the question is here? I get CCed on a bunch of not
> obviously relevant DRM patches so there's a good chance I've just
> deleted some relevnat discussion.
The patch is question is here:
https://lore.kernel.org/dri-devel/1609256210-19863-1-git-send-email-stefan.wahren@i2se.com/
In particular, I'm not so sure whether it's fine to return -EPROBE_DEFER
in the startup hook.
Thanks!
Maxime
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 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:[~2021-01-16 10:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-29 15:36 [PATCH RFC] drm/vc4: hdmi: Avoid ASoC error messages on startup Stefan Wahren
2021-01-09 11:41 ` Stefan Wahren
2021-01-13 9:19 ` Maxime Ripard
2021-01-13 11:42 ` Mark Brown
2021-01-15 18:14 ` Maxime Ripard [this message]
2021-01-15 18:39 ` Mark Brown
2021-01-18 11:28 ` Stefan Wahren
2021-01-18 12:10 ` Nicolas Saenz Julienne
2021-01-18 14:06 ` Maxime Ripard
2021-01-15 17:21 ` Nicolas Saenz Julienne
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=20210115181437.uqlkrbapv6ydswuy@gilmour \
--to=maxime@cerno.tech \
--cc=airlied@linux.ie \
--cc=broonie@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=lgirdwood@gmail.com \
--cc=nsaenzjulienne@suse.de \
--cc=stefan.wahren@i2se.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;
as well as URLs for NNTP newsgroup(s).