From: Sam Ravnborg <sam@ravnborg.org>
To: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Cc: linux-fbdev@vger.kernel.org,
Thierry Reding <thierry.reding@gmail.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] video: Demote panel timing not found error message
Date: Fri, 26 Jul 2019 15:32:52 +0000 [thread overview]
Message-ID: <20190726153252.GA24229@ravnborg.org> (raw)
In-Reply-To: <e9bf4cf5-f4de-0a3b-52f4-67f1ae7af5b9@samsung.com>
Hi Bartlomiej Zolnierkiewicz
>
> Hi Sam,
>
> On 7/26/19 1:36 PM, Sam Ravnborg wrote:
> > Hi Thierry.
> >
> > On Fri, Jul 26, 2019 at 12:18:49PM +0200, Thierry Reding wrote:
> >> From: Thierry Reding <treding@nvidia.com>
> >>
> >> Failing to find a panel-timing node is not an error in all cases, so do
> >> not output an error message in that case. Instead turn it into a debug
> >> message and make the drivers that care about it output an error message
> >> of their own.
> >
> > This is more or less the same as already implmented by Douglas here:
> > https://patchwork.kernel.org/cover/11053243/
> >
> > Doug's has an extra bug-fix that we shall not miss.
> >
> > I am waiting for feedback from Bartlomiej before proceeding.
>
> The patchset is in drm-misc-next tree now.
>
> > I guess he is on holiday somewhere and will return soon.
>
> I wish it was the case. ;-)
Well, too hot here for work atm. But the farmers are happy.
Can you maybe find time to respond to this patch:
https://lists.freedesktop.org/archives/dri-devel/2019-July/228051.html
It already got ack from backligt people, but as it touches fbdev
your feedback is required too.
Thanks,
Sam
next prev parent reply other threads:[~2019-07-26 15:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-26 10:18 [PATCH] video: Demote panel timing not found error message Thierry Reding
2019-07-26 11:36 ` Sam Ravnborg
2019-07-26 14:56 ` Bartlomiej Zolnierkiewicz
2019-07-26 15:32 ` Sam Ravnborg [this message]
2019-07-26 16:10 ` Bartlomiej Zolnierkiewicz
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=20190726153252.GA24229@ravnborg.org \
--to=sam@ravnborg.org \
--cc=b.zolnierkie@samsung.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fbdev@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).