From: Tony Lindgren <tony@atomide.com>
To: Aaro Koskinen <aaro.koskinen@iki.fi>
Cc: Tomi Valkeinen <tomi.valkeinen@ti.com>,
Peter Ujfalusi <peter.ujfalusi@ti.com>,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: [BISECTED, REGRESSION] v4.12-rc: omapdrm fails to probe on Nokia N900
Date: Thu, 29 Jun 2017 22:52:27 -0700 [thread overview]
Message-ID: <20170630055227.GF3730@atomide.com> (raw)
In-Reply-To: <20170629185013.aec7qhvrl3waifww@darkstar.musicnaut.iki.fi>
* Aaro Koskinen <aaro.koskinen@iki.fi> [170629 11:50]:
> Is it just me or do other OMAP users fail to see omapdrm changes being
> posted to linux-omap for testing or review purposes?
Yeah Cc:ing linux-omap in addition to the drm list is a good idea. Hopefully
we get few more people to review changes that way.
What also should help preventing regressions is getting the changes into
Linux next early on during the -rc cycle. And switching the defconfigs to
use omapdrm instead of omapfb. Maybe we should do that right after v4.13-rc1
is tagged.
Cheers,
Tony
next prev parent reply other threads:[~2017-06-30 5:52 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 22:11 [BISECTED, REGRESSION] v4.12-rc: omapdrm fails to probe on Nokia N900 Aaro Koskinen
2017-06-15 6:51 ` Tomi Valkeinen
2017-06-15 6:51 ` Tomi Valkeinen
2017-06-18 21:31 ` Aaro Koskinen
2017-06-29 18:50 ` Aaro Koskinen
2017-06-29 19:12 ` Aaro Koskinen
2017-06-30 5:52 ` Tony Lindgren [this message]
2017-06-30 6:41 ` Tomi Valkeinen
2017-06-30 6:41 ` Tomi Valkeinen
2017-06-30 8:47 ` Tomi Valkeinen
2017-06-30 8:47 ` Tomi Valkeinen
2017-06-30 9:37 ` Aaro Koskinen
2017-07-21 1:28 ` [BISECTED,REGRESSION] " Clayton Craft
2017-06-30 8:58 ` [BISECTED, REGRESSION] " Aaro Koskinen
2017-06-30 9:02 ` Tomi Valkeinen
2017-06-30 9:02 ` Tomi Valkeinen
2017-07-04 15:09 ` Pavel Machek
2017-07-31 12:59 ` Tomi Valkeinen
2017-07-31 12:59 ` Tomi Valkeinen
2017-06-30 12:36 ` Daniel Vetter
2017-06-30 12:36 ` Daniel Vetter
2017-07-31 13:21 ` Tomi Valkeinen
2017-07-31 13:21 ` Tomi Valkeinen
2017-08-02 10:12 ` Daniel Vetter
2017-08-02 10:12 ` Daniel Vetter
2017-08-02 11:54 ` Tomi Valkeinen
2017-08-02 11:54 ` Tomi Valkeinen
2017-08-02 12:08 ` Daniel Vetter
2017-08-02 12:08 ` Daniel Vetter
2017-06-15 7:28 ` Peter Ujfalusi
2017-06-15 7:28 ` Peter Ujfalusi
2017-06-18 21:44 ` Aaro Koskinen
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=20170630055227.GF3730@atomide.com \
--to=tony@atomide.com \
--cc=aaro.koskinen@iki.fi \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=peter.ujfalusi@ti.com \
--cc=tomi.valkeinen@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.