Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752822AbbDSTsa (ORCPT ); Sun, 19 Apr 2015 15:48:30 -0400 Received: from mout.kundenserver.de ([212.227.17.10]:55579 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752173AbbDSTs1 convert rfc822-to-8bit (ORCPT ); Sun, 19 Apr 2015 15:48:27 -0400 From: Arnd Bergmann To: linux-arm-kernel@lists.infradead.org Cc: Javier =?ISO-8859-1?Q?Gonz=E1lez?= , Valentin Manea , devicetree@vger.kernel.org, emmanuel.michel@st.com, Herbert Xu , Greg Kroah-Hartman , Linux Kernel Mailing List , jean-michel.delorme@st.com, tpmdd-devel@lists.sourceforge.net, Jens Wiklander Subject: Re: [RFC PATCH 2/2] tee: add OP-TEE driver Date: Sun, 19 Apr 2015 21:47:52 +0200 Message-ID: <7401865.1Pb83TJP0q@wuerfel> User-Agent: KMail/4.11.5 (Linux/3.16.0-10-generic; KDE/4.11.5; x86_64; ; ) In-Reply-To: <3960750D-EAE4-4FA0-9E15-89F9CE39257E@javigon.com> References: <1429257057-7935-1-git-send-email-jens.wiklander@linaro.org> <4984990.7rV4p0zMYU@wuerfel> <3960750D-EAE4-4FA0-9E15-89F9CE39257E@javigon.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8BIT Content-Type: text/plain; charset="iso-8859-1" X-Provags-ID: V03:K0:HHhBw6B0IF4QJ21nTHfglLj7eXAle7O5HSGrbdY5aLtbJ4Rx5E5 p2kY+QBeZ8TVy5NGe4Lsii7WDjmlcUw3OO2XxIX9aMUMDfvE/YGTzyUkIaMup+NHvHIG6va lkBw/w6/cXFNEcbu4dQNWj1EdxVxoMGhQaqCzA3ygkanqtjz/h3q4XSpaIG3YnXuhKGHbG+ 6rHYNnLQFs92LO3JwqTTA== X-UI-Out-Filterresults: notjunk:1; Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 945 Lines: 20 On Sunday 19 April 2015 13:17:20 Javier Gonz?lez wrote: > > Only providing user space support would defeat one of the main purposes > of the driver. We could better organize the patches and divide them into user > space support and in-kernel support if that is what you mean. In the end > the interfaces are orthogonal, even though the functionality should be very > similar. Splitting up the patches to separate the user interface from the in-kernel interface is certainly a good idea, but aside from that, I also agree with Greg on this point: if you want to establish an in-kernel interface, don't add any dead code at the beginning, but add it together with the users of that interface. Arnd -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/