From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thierry Reding <thierry.reding@gmail.com>
Subject: Re: [PATCH 2/2] drm/fb-helper: improve
 drm_fb_helper_initial_config locking
Date: Fri, 21 Mar 2014 18:02:43 +0100
Message-ID: <20140321170242.GB6315@ulmo>
References: <20140320130632.GE4463@nuc-i3427.alporthouse.com>
 <1395321995-4627-1-git-send-email-daniel.vetter@ffwll.ch>
 <1395321995-4627-2-git-send-email-daniel.vetter@ffwll.ch>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0127518976=="
Return-path: <intel-gfx-bounces@lists.freedesktop.org>
In-Reply-To: <1395321995-4627-2-git-send-email-daniel.vetter@ffwll.ch>
List-Unsubscribe: <http://lists.freedesktop.org/mailman/options/intel-gfx>,
 <mailto:intel-gfx-request@lists.freedesktop.org?subject=unsubscribe>
List-Archive: <http://lists.freedesktop.org/archives/intel-gfx>
List-Post: <mailto:intel-gfx@lists.freedesktop.org>
List-Help: <mailto:intel-gfx-request@lists.freedesktop.org?subject=help>
List-Subscribe: <http://lists.freedesktop.org/mailman/listinfo/intel-gfx>,
 <mailto:intel-gfx-request@lists.freedesktop.org?subject=subscribe>
Errors-To: intel-gfx-bounces@lists.freedesktop.org
Sender: "Intel-gfx" <intel-gfx-bounces@lists.freedesktop.org>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>, DRI Development <dri-devel@lists.freedesktop.org>
List-Id: intel-gfx@lists.freedesktop.org


--===============0127518976==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="oC1+HKm2/end4ao3"
Content-Disposition: inline


--oC1+HKm2/end4ao3
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Mar 20, 2014 at 02:26:35PM +0100, Daniel Vetter wrote:
[...]
> Hence the right fix is to grab the mode_config mutex, but only that
> and only right around the probe calls.
>=20
> It seems to be sufficient to shut up all the locking WARNINGs I see on
> i915 and nouveau in drm_fb_helper_initial_config.

Fixes any of the WARNINGs remaining after patch 1/2 for me on Tegra as
well, so:

Tested-by: Thierry Reding <treding@nvidia.com>

--oC1+HKm2/end4ao3
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAEBAgAGBQJTLHCyAAoJEN0jrNd/PrOhX5YP/3z6R7MmVisfAI5i26qmacbh
usiNd+2B1u3YtkDYTqvB3FmEN7Ezck8hRKOEoq+AH9UA3ug4a46wsejCVQkDv0RX
dnqrBI13zAIBoniCdA1ivKVSs1edNEcvx8kqR2JljN7a49KuR8ZLHbnjpXswQxwd
9r6ioGXhvB0kjUIB20oHyR06fDMdg5vHxmIXn9nqPrMQoCPNI69+Hl3Pdmewk13Q
ao32wcZaldTuS/4uvU/KN9nkujjQY8S01oPsdizItqZzTJc6fA7g7yhiB86Vt2Ar
E+HYSdvHiuCYZms3QK2vdAvDqBxUm9WxaZ83mCywx9vwmF5UBPzLVJbL1gWxfrbm
zd7Qx2AH05uPSuTa44Y7h6JKrGjJ2PJ+SFb5gSu3fOpJal6DViVOak7JLNYFDKF7
fLb5tryStjypiLZDwY5jpngat5wni36yJlByrk4GNq53VFo0swLKPKauuB6u7+Ht
H06Fq0UUB8T2RK6zHx2x/8wAeKomx3GdOagG150+Ps245II98JFbid9qpmpHlYzd
CGbFjNtGzmyZ+HgV6x6dHA/jOTm47/LLHduoxwnS9s3QCUJ8BUO4egkXk9Fnuv0C
f9g3u+7KTIcRl0Y0m2UmFtIrZ4GhH8CqUL+u7dYfPkH8COUmH0+trTDrS3D0Ea7t
D/C7E7o0SItD5hIBKWhO
=z0mf
-----END PGP SIGNATURE-----

--oC1+HKm2/end4ao3--

--===============0127518976==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

--===============0127518976==--