Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S936097AbcCQP5e (ORCPT ); Thu, 17 Mar 2016 11:57:34 -0400 Received: from mout.kundenserver.de ([217.72.192.75]:50884 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S935075AbcCQP53 (ORCPT ); Thu, 17 Mar 2016 11:57:29 -0400 From: Arnd Bergmann To: linux-arm-kernel@lists.infradead.org Cc: Brian Norris , David Woodhouse , linux-arch@vger.kernel.org, linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] mtd: only use __xipram annotation when XIP_KERNEL is set Date: Thu, 17 Mar 2016 16:56:33 +0100 Message-ID: <4420020.GISMAEPJsq@wuerfel> User-Agent: KMail/4.11.5 (Linux/3.16.0-10-generic; KDE/4.11.5; x86_64; ; ) In-Reply-To: <20160305004336.GG55664@google.com> References: <1453736525-1959191-2-git-send-email-arnd@arndb.de> <1457137718.43867.266.camel@infradead.org> <20160305004336.GG55664@google.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Provags-ID: V03:K0:fFeclooUp2pKvc0FUIDRxw6JTLWFeXdiNJmnX5aWeqMaQlNrQXo UYwAgF4Ry1VM+Q6VkcRyekFgw7vEkT4zeUH6GkMXCrd3YJYTMEvVbW6J4FjYDXOI05Lh0cf XeWt4X+XesM6THB3mnD7EgVzGtWUZGnGLo831WxHdKsT/peCet4cfFWnBGIcv11T7NfOz70 TLQPk6ELYkQSZSMnbO9Ag== X-UI-Out-Filterresults: notjunk:1;V01:K0:/3mKzZ8UMp0=:x1gilVXcXAM4C3rXQJTaEe kQN77uffipdZKEFCiP5qvxE3TZy4wVo0VKnALUgp6u9xquZvJGJkElILm1uOJZ4JOWsFeboep CD90vcpnuqkqKxsQ1W+tlvyAfCP59jKR3pEhM2zmwlOjG+4MuE15dw0zJ2WHYhzPmyGvayZVy 1RTKWlKGByyKwboUtFfrdn+8g/Sv0wCIEmMXrm3NZuP0pvMhpDWjmcIAZXtNAD0QRBBT8w6z0 XD06552dUvbBI17Oh16fv/9gT7hlybN2sGOjowyqC3e5r6H+yxf5JzbW++p3oH4DxZS7Q5Px2 /sAO3ufxq4nhk4sA7uC37FGYjZdmCzomEoeLzuOhirjk8rDdYtYy5MHj11xW00hMXmmLk3J9S u3qBE/Yfk5k2IQB8kY+NuOpZzFYr1IFCc3aJ42xhazaDJHqoYbK1aFoohamS1jE3OVFMxuR61 N5btF+SRItJXT7NuZw0o3T9QkdTbjE/NY7Tbb1v/6dspFS9FgZczVwJPOAEKaQKBOJNgeC3Zk BMVBQS4W+XTMOzO/vdFuSd5Z2dSN/99XdL1elLBV2yLYS+/h/zC2QZW2hutWMs68n8zQXfiYA qTfTQQzxNunqqHpymwbb4X4MyJ6GTMnvpdxASe3WekbQszz3u17+cjDiW3mi30n207gp/RiV/ EwibKGcMD2RMPgPOqIRgeVD2XngBDiJ915R17sCEkvSbXF8luz41FvJMOkhEoOzx0s9Fcq0wd avtYWqZC4HzN5lcx Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1292 Lines: 30 On Friday 04 March 2016 16:43:36 Brian Norris wrote: > On Sat, Mar 05, 2016 at 12:28:38AM +0000, David Woodhouse wrote: > > On Fri, 2016-03-04 at 16:22 -0800, Brian Norris wrote: > > > > > > ...but, does anyone care about XIP / MTD_XIP then, if the first two > > > examples we have both have long-standing build issues? > > > > I think there are people trying to make it work on other platforms, > > yes. > > OK... can we kill the broken platforms though? I'm not confident that my > and Arnd's workaround attempts will yield anything more than a pat on > our own backs to say "yay, it compiles!" And given the number of > practically unused things we're already maintaining in MTD, I'm always > happy for an excuse to kill off some of it. Sorry for the late reply. As the three platforms that use this have all been broken for around ten years, it seems reasonable to assume nobody is going to miss the current implementation, but I'd leave it up to the individual platform maintainers. If we remove all three, that would also give us more flexibility regarding the interface definition for any future users of the feature. I think the most likely to use it is the Renesas RZ/A1H platform with its 10MB of on-chip SRAM, and this one doesn't work with the current method anyway. Arnd