From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9FD26C433F5 for ; Tue, 22 Mar 2022 17:43:59 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236496AbiCVRpZ (ORCPT ); Tue, 22 Mar 2022 13:45:25 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34472 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235001AbiCVRpY (ORCPT ); Tue, 22 Mar 2022 13:45:24 -0400 Received: from metis.ext.pengutronix.de (metis.ext.pengutronix.de [IPv6:2001:67c:670:201:290:27ff:fe1d:cc33]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B39B527FF3 for ; Tue, 22 Mar 2022 10:43:56 -0700 (PDT) Received: from drehscheibe.grey.stw.pengutronix.de ([2a0a:edc0:0:c01:1d::a2]) by metis.ext.pengutronix.de with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nWiXy-0001ho-U5; Tue, 22 Mar 2022 18:43:54 +0100 Received: from [2a0a:edc0:0:900:1d::77] (helo=ptz.office.stw.pengutronix.de) by drehscheibe.grey.stw.pengutronix.de with esmtp (Exim 4.94.2) (envelope-from ) id 1nWiXu-002KwV-FK; Tue, 22 Mar 2022 18:43:53 +0100 Received: from ukl by ptz.office.stw.pengutronix.de with local (Exim 4.94.2) (envelope-from ) id 1nWiXw-00AxAG-1c; Tue, 22 Mar 2022 18:43:52 +0100 Date: Tue, 22 Mar 2022 18:43:51 +0100 From: Uwe =?utf-8?Q?Kleine-K=C3=B6nig?= To: Rob Herring Cc: devicetree@vger.kernel.org, Pengutronix Kernel Team , David Airlie , Fabio Estevam , dri-devel , NXP Linux Team , Daniel Vetter , Philipp Zabel , Shawn Guo , linux-arm-kernel , Lucas Stach Subject: Re: [PATCH 1/2] dt-bindings: display: imx: Add fsl,imx21-lcdc docs Message-ID: <20220322174351.hla4d4fbfmdh3gvw@pengutronix.de> References: <20220128105849.368438-1-u.kleine-koenig@pengutronix.de> <20220128105849.368438-2-u.kleine-koenig@pengutronix.de> <20220128175829.vjm66rs7eu7pk2my@pengutronix.de> <20220221135536.3arbh2ucih4jn4ti@pengutronix.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="gf5abkaroff55vt5" Content-Disposition: inline In-Reply-To: <20220221135536.3arbh2ucih4jn4ti@pengutronix.de> X-SA-Exim-Connect-IP: 2a0a:edc0:0:c01:1d::a2 X-SA-Exim-Mail-From: ukl@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false X-PTX-Original-Recipient: devicetree@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org --gf5abkaroff55vt5 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Rob, On Mon, Feb 21, 2022 at 02:55:36PM +0100, Uwe Kleine-K=F6nig wrote: > On Thu, Feb 10, 2022 at 06:54:13PM +0100, Lucas Stach wrote: > > Am Dienstag, dem 01.02.2022 um 11:35 -0600 schrieb Rob Herring: > > > On Fri, Jan 28, 2022 at 06:58:29PM +0100, Uwe Kleine-K=F6nig wrote: > > > > On Fri, Jan 28, 2022 at 07:04:10AM -0600, Rob Herring wrote: > > > > > On Fri, Jan 28, 2022 at 4:59 AM Uwe Kleine-K=F6nig > > > > > wrote: > > > > > >=20 > > > > > > From: Marian Cichy > > > > > >=20 > > > > > > This files documents the device tree for the new imx21-lcdc DRM= driver. > > > > >=20 > > > > > No, bindings document h/w and the h/w has not changed. We already= have > > > > > a binding for the LCDC. > > > >=20 > > > > Just to be sure we're talking about the same thing: You're refering= to > > > > Documentation/devicetree/bindings/display/imx/fsl,imx-fb.txt, right? > > >=20 > > > Looks right... > > >=20 > > > > I'm unsure what to do now. Should the two different bindings just be > > > > described in the same file? Should I stick to fsl,imx21-fb even for= the > > > > new binding? (The hardware unit is named LCDC, so the name chosen h= ere > > > > is the better one.) Please advise. > > >=20 > > > Yes, the name is unfortunate, but it should be 1 binding, 1 file, and= =20 > > > unchanged (unless you want to add new optional properties).=20 > > > > The old FB driver binding is pretty insane. Except the reg and > > interrupt properties it is very confused about things. It exposes > > internal implementation details (like specifying verbatim register > > settings in the DT) and other properties are just misplaced, like the > > lcd-supply property that controls the panel power supply. > >=20 > > I really don't think that trying to stay backwards compatible here is a > > win for anyone. Anyone willing to switch their systems running on a 15 > > year old SoC to the new DRM driver probably doesn't mind if they have > > to modify the DTS to make it work. Can we please let the FB driver die > > in peace and have a clean slate driver/binding for the DRM driver? >=20 > Does this feedback change anything on your side? My expectation is that > the graphics people will be happy about every fb driver being replaced > by a DRM driver and there will be hardly any incentive to add a layer > over the DRM driver to make it honor the old fb binding. >=20 > Assume I convert the old binding to yaml and then add the newly > supported binding to that using a big oneOf, would that be an acceptable > compromise? I'd like to get forward with this driver. What would be a good way to continue here?=20 Best regards Uwe --=20 Pengutronix e.K. | Uwe Kleine-K=F6nig | Industrial Linux Solutions | https://www.pengutronix.de/ | --gf5abkaroff55vt5 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCgAdFiEEfnIqFpAYrP8+dKQLwfwUeK3K7AkFAmI6CtMACgkQwfwUeK3K 7AmEHwf6A2WIo831P0Vi/Ta/NAYjYQevEb8kYc5hZuuds8bhhtbW5RLG1arIQwU8 898QQFeMRc9mBROTkQL5e41iDAq1HwCNgh/wnwA8n1x1ogWLFJW3r4yUVa7Qaq82 rffajNDzcsgzegN/ibpmPRYf+ep9xEfhzEKJKuGjcF7U1l4yxZVS0Q4u7wbNmrac CXDxOTZGLvyxAoWXUA5CXBXh2S5WEIgOV/t8O/3AbChY5mUSt3HXBOKo2DjMXI/q +y5c0GvraqTXLecebf74sBOrsmYD8Krnql+tQhv3jLhdZqivS2eI+NPnaJGx4kfU CsfSVyaysdqwlCOVF/lwazIK6Hfncw== =Edlc -----END PGP SIGNATURE----- --gf5abkaroff55vt5-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 1BE7EC433EF for ; Tue, 22 Mar 2022 17:43:59 +0000 (UTC) Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 1C93010E030; Tue, 22 Mar 2022 17:43:59 +0000 (UTC) Received: from metis.ext.pengutronix.de (metis.ext.pengutronix.de [IPv6:2001:67c:670:201:290:27ff:fe1d:cc33]) by gabe.freedesktop.org (Postfix) with ESMTPS id E952210E030 for ; Tue, 22 Mar 2022 17:43:57 +0000 (UTC) Received: from drehscheibe.grey.stw.pengutronix.de ([2a0a:edc0:0:c01:1d::a2]) by metis.ext.pengutronix.de with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nWiXy-0001ho-U5; Tue, 22 Mar 2022 18:43:54 +0100 Received: from [2a0a:edc0:0:900:1d::77] (helo=ptz.office.stw.pengutronix.de) by drehscheibe.grey.stw.pengutronix.de with esmtp (Exim 4.94.2) (envelope-from ) id 1nWiXu-002KwV-FK; Tue, 22 Mar 2022 18:43:53 +0100 Received: from ukl by ptz.office.stw.pengutronix.de with local (Exim 4.94.2) (envelope-from ) id 1nWiXw-00AxAG-1c; Tue, 22 Mar 2022 18:43:52 +0100 Date: Tue, 22 Mar 2022 18:43:51 +0100 From: Uwe =?utf-8?Q?Kleine-K=C3=B6nig?= To: Rob Herring Subject: Re: [PATCH 1/2] dt-bindings: display: imx: Add fsl,imx21-lcdc docs Message-ID: <20220322174351.hla4d4fbfmdh3gvw@pengutronix.de> References: <20220128105849.368438-1-u.kleine-koenig@pengutronix.de> <20220128105849.368438-2-u.kleine-koenig@pengutronix.de> <20220128175829.vjm66rs7eu7pk2my@pengutronix.de> <20220221135536.3arbh2ucih4jn4ti@pengutronix.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="gf5abkaroff55vt5" Content-Disposition: inline In-Reply-To: <20220221135536.3arbh2ucih4jn4ti@pengutronix.de> X-SA-Exim-Connect-IP: 2a0a:edc0:0:c01:1d::a2 X-SA-Exim-Mail-From: ukl@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false X-PTX-Original-Recipient: dri-devel@lists.freedesktop.org X-BeenThere: dri-devel@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Direct Rendering Infrastructure - Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: devicetree@vger.kernel.org, David Airlie , Shawn Guo , dri-devel , NXP Linux Team , Pengutronix Kernel Team , linux-arm-kernel Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" --gf5abkaroff55vt5 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Rob, On Mon, Feb 21, 2022 at 02:55:36PM +0100, Uwe Kleine-K=F6nig wrote: > On Thu, Feb 10, 2022 at 06:54:13PM +0100, Lucas Stach wrote: > > Am Dienstag, dem 01.02.2022 um 11:35 -0600 schrieb Rob Herring: > > > On Fri, Jan 28, 2022 at 06:58:29PM +0100, Uwe Kleine-K=F6nig wrote: > > > > On Fri, Jan 28, 2022 at 07:04:10AM -0600, Rob Herring wrote: > > > > > On Fri, Jan 28, 2022 at 4:59 AM Uwe Kleine-K=F6nig > > > > > wrote: > > > > > >=20 > > > > > > From: Marian Cichy > > > > > >=20 > > > > > > This files documents the device tree for the new imx21-lcdc DRM= driver. > > > > >=20 > > > > > No, bindings document h/w and the h/w has not changed. We already= have > > > > > a binding for the LCDC. > > > >=20 > > > > Just to be sure we're talking about the same thing: You're refering= to > > > > Documentation/devicetree/bindings/display/imx/fsl,imx-fb.txt, right? > > >=20 > > > Looks right... > > >=20 > > > > I'm unsure what to do now. Should the two different bindings just be > > > > described in the same file? Should I stick to fsl,imx21-fb even for= the > > > > new binding? (The hardware unit is named LCDC, so the name chosen h= ere > > > > is the better one.) Please advise. > > >=20 > > > Yes, the name is unfortunate, but it should be 1 binding, 1 file, and= =20 > > > unchanged (unless you want to add new optional properties).=20 > > > > The old FB driver binding is pretty insane. Except the reg and > > interrupt properties it is very confused about things. It exposes > > internal implementation details (like specifying verbatim register > > settings in the DT) and other properties are just misplaced, like the > > lcd-supply property that controls the panel power supply. > >=20 > > I really don't think that trying to stay backwards compatible here is a > > win for anyone. Anyone willing to switch their systems running on a 15 > > year old SoC to the new DRM driver probably doesn't mind if they have > > to modify the DTS to make it work. Can we please let the FB driver die > > in peace and have a clean slate driver/binding for the DRM driver? >=20 > Does this feedback change anything on your side? My expectation is that > the graphics people will be happy about every fb driver being replaced > by a DRM driver and there will be hardly any incentive to add a layer > over the DRM driver to make it honor the old fb binding. >=20 > Assume I convert the old binding to yaml and then add the newly > supported binding to that using a big oneOf, would that be an acceptable > compromise? I'd like to get forward with this driver. What would be a good way to continue here?=20 Best regards Uwe --=20 Pengutronix e.K. | Uwe Kleine-K=F6nig | Industrial Linux Solutions | https://www.pengutronix.de/ | --gf5abkaroff55vt5 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCgAdFiEEfnIqFpAYrP8+dKQLwfwUeK3K7AkFAmI6CtMACgkQwfwUeK3K 7AmEHwf6A2WIo831P0Vi/Ta/NAYjYQevEb8kYc5hZuuds8bhhtbW5RLG1arIQwU8 898QQFeMRc9mBROTkQL5e41iDAq1HwCNgh/wnwA8n1x1ogWLFJW3r4yUVa7Qaq82 rffajNDzcsgzegN/ibpmPRYf+ep9xEfhzEKJKuGjcF7U1l4yxZVS0Q4u7wbNmrac CXDxOTZGLvyxAoWXUA5CXBXh2S5WEIgOV/t8O/3AbChY5mUSt3HXBOKo2DjMXI/q +y5c0GvraqTXLecebf74sBOrsmYD8Krnql+tQhv3jLhdZqivS2eI+NPnaJGx4kfU CsfSVyaysdqwlCOVF/lwazIK6Hfncw== =Edlc -----END PGP SIGNATURE----- --gf5abkaroff55vt5-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 5E4DAC433F5 for ; Tue, 22 Mar 2022 17:45:27 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:Content-Type: List-Subscribe:List-Help:List-Post:List-Archive:List-Unsubscribe:List-Id: In-Reply-To:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date: Reply-To:Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date :Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=Luvt4aLSKlxFWzMeIy8AeeONTJorUGd9Vyxy0EyOo3Q=; b=IRbFypbi/x+GBS3hzUWVWifst7 g+7U3CyHHo/2d+OSi2aIdWyMfGMpeMbIZM+MUDeZmjYzD2DeESD7hdlOkI6WGxgIWqe9GwsDRTQrX jA1yFFncfaccm9wF7KtrvSSIF38p0UiAV0uDF/+3ir8TmyuCYUX23R83Sw97REuPGUmIuFoSI/DWd 54UkuRc9+nxahoIifeXi9PtE4ebpOBOMkQJgEMjUyCO9Ogz1YkUk6YmO1+hkFBRqg0hiPXmnAfxWT 8mYww4nWeTTPH3K4y6P+a1CcZukYHE1RSF/j/Q3uzB/nKfjIhMGXUNneaLgRcN/vQTKiSwlAKQpIp 7p2W4MNA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1nWiYC-00BlbI-IV; Tue, 22 Mar 2022 17:44:08 +0000 Received: from metis.ext.pengutronix.de ([2001:67c:670:201:290:27ff:fe1d:cc33]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1nWiY8-00BlaH-7k for linux-arm-kernel@lists.infradead.org; Tue, 22 Mar 2022 17:44:05 +0000 Received: from drehscheibe.grey.stw.pengutronix.de ([2a0a:edc0:0:c01:1d::a2]) by metis.ext.pengutronix.de with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nWiXy-0001ho-U5; Tue, 22 Mar 2022 18:43:54 +0100 Received: from [2a0a:edc0:0:900:1d::77] (helo=ptz.office.stw.pengutronix.de) by drehscheibe.grey.stw.pengutronix.de with esmtp (Exim 4.94.2) (envelope-from ) id 1nWiXu-002KwV-FK; Tue, 22 Mar 2022 18:43:53 +0100 Received: from ukl by ptz.office.stw.pengutronix.de with local (Exim 4.94.2) (envelope-from ) id 1nWiXw-00AxAG-1c; Tue, 22 Mar 2022 18:43:52 +0100 Date: Tue, 22 Mar 2022 18:43:51 +0100 From: Uwe =?utf-8?Q?Kleine-K=C3=B6nig?= To: Rob Herring Cc: devicetree@vger.kernel.org, Pengutronix Kernel Team , David Airlie , Fabio Estevam , dri-devel , NXP Linux Team , Daniel Vetter , Philipp Zabel , Shawn Guo , linux-arm-kernel , Lucas Stach Subject: Re: [PATCH 1/2] dt-bindings: display: imx: Add fsl,imx21-lcdc docs Message-ID: <20220322174351.hla4d4fbfmdh3gvw@pengutronix.de> References: <20220128105849.368438-1-u.kleine-koenig@pengutronix.de> <20220128105849.368438-2-u.kleine-koenig@pengutronix.de> <20220128175829.vjm66rs7eu7pk2my@pengutronix.de> <20220221135536.3arbh2ucih4jn4ti@pengutronix.de> MIME-Version: 1.0 In-Reply-To: <20220221135536.3arbh2ucih4jn4ti@pengutronix.de> X-SA-Exim-Connect-IP: 2a0a:edc0:0:c01:1d::a2 X-SA-Exim-Mail-From: ukl@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false X-PTX-Original-Recipient: linux-arm-kernel@lists.infradead.org X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220322_104404_287621_E005505D X-CRM114-Status: GOOD ( 40.29 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2392222517555674361==" Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org --===============2392222517555674361== Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="gf5abkaroff55vt5" Content-Disposition: inline --gf5abkaroff55vt5 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Rob, On Mon, Feb 21, 2022 at 02:55:36PM +0100, Uwe Kleine-K=F6nig wrote: > On Thu, Feb 10, 2022 at 06:54:13PM +0100, Lucas Stach wrote: > > Am Dienstag, dem 01.02.2022 um 11:35 -0600 schrieb Rob Herring: > > > On Fri, Jan 28, 2022 at 06:58:29PM +0100, Uwe Kleine-K=F6nig wrote: > > > > On Fri, Jan 28, 2022 at 07:04:10AM -0600, Rob Herring wrote: > > > > > On Fri, Jan 28, 2022 at 4:59 AM Uwe Kleine-K=F6nig > > > > > wrote: > > > > > >=20 > > > > > > From: Marian Cichy > > > > > >=20 > > > > > > This files documents the device tree for the new imx21-lcdc DRM= driver. > > > > >=20 > > > > > No, bindings document h/w and the h/w has not changed. We already= have > > > > > a binding for the LCDC. > > > >=20 > > > > Just to be sure we're talking about the same thing: You're refering= to > > > > Documentation/devicetree/bindings/display/imx/fsl,imx-fb.txt, right? > > >=20 > > > Looks right... > > >=20 > > > > I'm unsure what to do now. Should the two different bindings just be > > > > described in the same file? Should I stick to fsl,imx21-fb even for= the > > > > new binding? (The hardware unit is named LCDC, so the name chosen h= ere > > > > is the better one.) Please advise. > > >=20 > > > Yes, the name is unfortunate, but it should be 1 binding, 1 file, and= =20 > > > unchanged (unless you want to add new optional properties).=20 > > > > The old FB driver binding is pretty insane. Except the reg and > > interrupt properties it is very confused about things. It exposes > > internal implementation details (like specifying verbatim register > > settings in the DT) and other properties are just misplaced, like the > > lcd-supply property that controls the panel power supply. > >=20 > > I really don't think that trying to stay backwards compatible here is a > > win for anyone. Anyone willing to switch their systems running on a 15 > > year old SoC to the new DRM driver probably doesn't mind if they have > > to modify the DTS to make it work. Can we please let the FB driver die > > in peace and have a clean slate driver/binding for the DRM driver? >=20 > Does this feedback change anything on your side? My expectation is that > the graphics people will be happy about every fb driver being replaced > by a DRM driver and there will be hardly any incentive to add a layer > over the DRM driver to make it honor the old fb binding. >=20 > Assume I convert the old binding to yaml and then add the newly > supported binding to that using a big oneOf, would that be an acceptable > compromise? I'd like to get forward with this driver. What would be a good way to continue here?=20 Best regards Uwe --=20 Pengutronix e.K. | Uwe Kleine-K=F6nig | Industrial Linux Solutions | https://www.pengutronix.de/ | --gf5abkaroff55vt5 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCgAdFiEEfnIqFpAYrP8+dKQLwfwUeK3K7AkFAmI6CtMACgkQwfwUeK3K 7AmEHwf6A2WIo831P0Vi/Ta/NAYjYQevEb8kYc5hZuuds8bhhtbW5RLG1arIQwU8 898QQFeMRc9mBROTkQL5e41iDAq1HwCNgh/wnwA8n1x1ogWLFJW3r4yUVa7Qaq82 rffajNDzcsgzegN/ibpmPRYf+ep9xEfhzEKJKuGjcF7U1l4yxZVS0Q4u7wbNmrac CXDxOTZGLvyxAoWXUA5CXBXh2S5WEIgOV/t8O/3AbChY5mUSt3HXBOKo2DjMXI/q +y5c0GvraqTXLecebf74sBOrsmYD8Krnql+tQhv3jLhdZqivS2eI+NPnaJGx4kfU CsfSVyaysdqwlCOVF/lwazIK6Hfncw== =Edlc -----END PGP SIGNATURE----- --gf5abkaroff55vt5-- --===============2392222517555674361== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel --===============2392222517555674361==--