From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tomi Valkeinen Date: Mon, 03 Mar 2014 10:45:22 +0000 Subject: Re: [PATCH 00/11] SimpleDRM & Sysfb Message-Id: <53145D42.9080806@ti.com> MIME-Version: 1 Content-Type: multipart/mixed; boundary="TqVtlUqnI6lMMPVvdPAPxFWfwQIN8FjR1" List-Id: References: <1390486503-1504-1-git-send-email-dh.herrmann@gmail.com> <53145591.4070004@ti.com> In-Reply-To: To: David Herrmann Cc: "dri-devel@lists.freedesktop.org" , Ingo Molnar , "linux-fbdev@vger.kernel.org" , Dave Airlie , Daniel Vetter , linux-kernel , Tom Gundersen --TqVtlUqnI6lMMPVvdPAPxFWfwQIN8FjR1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 03/03/14 12:29, David Herrmann wrote: >> What's the status with this one? Headed for 3.15? >> >> Are the SimpleDRM and sysfb linked somehow? (I.e. do they need to be i= n >> the same series?) >> >> And jfyi, the drivers/video/ changes will conflict with the >> drivers/video/ directory reorganization series, which may be merged fo= r >> 3.15. >=20 > If simpledrm is included, then the series needs to be applied as a > whole. As Dave considered merging this for 3.15, I'd appreciate it if > you could ACK the fbdev related patches (they're really small!): > fbdev: efifb: add dev->remove() callback > fbdev: vesafb: add dev->remove() callback Those look fine. I'm not familiar with x86 fb, so I can't comment much to the series, but what worries me more is the "[PATCH 06/11] video: sysfb: add generic firmware-fb interface", which adds new stuff into drivers/video/. No problem as such, but as said, it'll conflict with the fbdev reorg patches= =2E So, presuming nobody shoots down the fbdev reorg series, I'd like to have all fbdev patches going through the fbdev tree for 3.15, so that I can handle the (possibly messy) conflicts. What do you think, would it be possible to keep the sysfb stuff in arch/x86, and still be able to do the rest of the stuff here? And then move the sysfs from arch/x86 to drivers/video later? Tomi --TqVtlUqnI6lMMPVvdPAPxFWfwQIN8FjR1 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJTFF1CAAoJEPo9qoy8lh71MvIP/Rg9GiCdBSKyfxeSKJrq9WOv m/DY+BNgALAz17/nIBC4EsS3QpcY8b0Xk3+3NZHQv74SZLCFz0HstJCVaFxibdyM UyCZtoSrfMy6n6I/CsY1w19DghQQdzKjzv4TOjzAB+g5TngPl9e0+jczWSgn/3EY yMKwkYYtqhmNOoQtQ0xeBn1vv9nOhZSPFCjDE3qtMuoGINo8thtJsD26X4zzp8pE w8ySzwMzylelvDJeEnWo2lwsIKgAE1NJxabyMfjum7mxXokHeQE82BeiW49NvX+P NE40SVO4gF6TPJe4rhLYmfnyTG/+bzqGTY5KmrwyMqFnO3joJgogHAtonoWvOvjB qM4Sj+kkTpKg72WZbklygkZoWw9acUg4WBfI63hxoJuXo7r5TKTGOT+zHlwWWnyN MirqIw/NZdDgRKI4ReL6SM0WBA9TIZobYuKFzYyuaNC1OB0vOmFFEp0MQh0fzvsl Q8KsuP+vcDl+HyAecuWlz/pVw2GX+mzPMfaxPj03hBEupPqgFvZ5YiNpZTgYKuGR jrrzRKMXLEtpqyeA8X8q/91Le3Ihk+shjN8+D+jBYy0BCCVZkApfom4U6MsHyXt5 xqM2zBxWw/Gnmn3g8IFy3yhSAHgI08mf817YaOdrNkEqZOUMJhop3ZdayZmyE7bq jPvTFfnpU/s3Y0CXiplS =efnW -----END PGP SIGNATURE----- --TqVtlUqnI6lMMPVvdPAPxFWfwQIN8FjR1-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tomi Valkeinen Subject: Re: [PATCH 00/11] SimpleDRM & Sysfb Date: Mon, 3 Mar 2014 12:45:22 +0200 Message-ID: <53145D42.9080806@ti.com> References: <1390486503-1504-1-git-send-email-dh.herrmann@gmail.com> <53145591.4070004@ti.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="TqVtlUqnI6lMMPVvdPAPxFWfwQIN8FjR1" Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: David Herrmann Cc: "dri-devel@lists.freedesktop.org" , Ingo Molnar , "linux-fbdev@vger.kernel.org" , Dave Airlie , Daniel Vetter , linux-kernel , Tom Gundersen List-Id: dri-devel@lists.freedesktop.org --TqVtlUqnI6lMMPVvdPAPxFWfwQIN8FjR1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 03/03/14 12:29, David Herrmann wrote: >> What's the status with this one? Headed for 3.15? >> >> Are the SimpleDRM and sysfb linked somehow? (I.e. do they need to be i= n >> the same series?) >> >> And jfyi, the drivers/video/ changes will conflict with the >> drivers/video/ directory reorganization series, which may be merged fo= r >> 3.15. >=20 > If simpledrm is included, then the series needs to be applied as a > whole. As Dave considered merging this for 3.15, I'd appreciate it if > you could ACK the fbdev related patches (they're really small!): > fbdev: efifb: add dev->remove() callback > fbdev: vesafb: add dev->remove() callback Those look fine. I'm not familiar with x86 fb, so I can't comment much to the series, but what worries me more is the "[PATCH 06/11] video: sysfb: add generic firmware-fb interface", which adds new stuff into drivers/video/. No problem as such, but as said, it'll conflict with the fbdev reorg patches= =2E So, presuming nobody shoots down the fbdev reorg series, I'd like to have all fbdev patches going through the fbdev tree for 3.15, so that I can handle the (possibly messy) conflicts. What do you think, would it be possible to keep the sysfb stuff in arch/x86, and still be able to do the rest of the stuff here? And then move the sysfs from arch/x86 to drivers/video later? Tomi --TqVtlUqnI6lMMPVvdPAPxFWfwQIN8FjR1 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJTFF1CAAoJEPo9qoy8lh71MvIP/Rg9GiCdBSKyfxeSKJrq9WOv m/DY+BNgALAz17/nIBC4EsS3QpcY8b0Xk3+3NZHQv74SZLCFz0HstJCVaFxibdyM UyCZtoSrfMy6n6I/CsY1w19DghQQdzKjzv4TOjzAB+g5TngPl9e0+jczWSgn/3EY yMKwkYYtqhmNOoQtQ0xeBn1vv9nOhZSPFCjDE3qtMuoGINo8thtJsD26X4zzp8pE w8ySzwMzylelvDJeEnWo2lwsIKgAE1NJxabyMfjum7mxXokHeQE82BeiW49NvX+P NE40SVO4gF6TPJe4rhLYmfnyTG/+bzqGTY5KmrwyMqFnO3joJgogHAtonoWvOvjB qM4Sj+kkTpKg72WZbklygkZoWw9acUg4WBfI63hxoJuXo7r5TKTGOT+zHlwWWnyN MirqIw/NZdDgRKI4ReL6SM0WBA9TIZobYuKFzYyuaNC1OB0vOmFFEp0MQh0fzvsl Q8KsuP+vcDl+HyAecuWlz/pVw2GX+mzPMfaxPj03hBEupPqgFvZ5YiNpZTgYKuGR jrrzRKMXLEtpqyeA8X8q/91Le3Ihk+shjN8+D+jBYy0BCCVZkApfom4U6MsHyXt5 xqM2zBxWw/Gnmn3g8IFy3yhSAHgI08mf817YaOdrNkEqZOUMJhop3ZdayZmyE7bq jPvTFfnpU/s3Y0CXiplS =efnW -----END PGP SIGNATURE----- --TqVtlUqnI6lMMPVvdPAPxFWfwQIN8FjR1--