From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751283AbdBXFSS (ORCPT ); Fri, 24 Feb 2017 00:18:18 -0500 Received: from mail-lf0-f66.google.com ([209.85.215.66]:35732 "EHLO mail-lf0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751190AbdBXFSQ (ORCPT ); Fri, 24 Feb 2017 00:18:16 -0500 MIME-Version: 1.0 X-Originating-IP: [50.196.179.26] In-Reply-To: <20170221171438.e5hvruoixafpcdps@piout.net> References: <20170221090610.6d531b94@bbrezillon> <20170221112641.6276c001@bbrezillon> <20170221112720.ynehsryprhrhzjla@piout.net> <20170221162133.jch6yzpotj4s7zob@piout.net> <20170221171438.e5hvruoixafpcdps@piout.net> From: =?UTF-8?Q?H=C3=A5vard_Skinnemoen?= Date: Thu, 23 Feb 2017 21:18:13 -0800 X-Google-Sender-Auth: iJcq8v7XOgxACSL_XfzZYIxuY8A Message-ID: Subject: Re: [PATCH v2 1/3] mtd: nand: Cleanup/rework the atmel_nand driver To: Alexandre Belloni Cc: Andy Shevchenko , Hans-Christian Egtvedt , Boris Brezillon , Richard Weinberger , "open list:MEMORY TECHNOLOGY..." , Nicolas Ferre , Haavard Skinnemoen , "linux-kernel@vger.kernel.org" , Wenyou Yang , Josh Wu , David Woodhouse , Brian Norris , Marek Vasut , Cyrille Pitchen , linux-arm Mailing List , Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , devicetree Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.home.local id v1O5IQ70014994 On Tue, Feb 21, 2017 at 9:14 AM, Alexandre Belloni wrote: > On 21/02/2017 at 18:43:35 +0200, Andy Shevchenko wrote: >> >> Come on, v4.10 has just been release and >> >> It doesn't build anymore. And current case even worse >> Face it. It's dead. >> > > I agree it hasn't seen any significant development in a while but I'm > not the on able to take that decision. I've been wanting to add devicetree support for some time, but I no longer remember how to build the toolchain, and I don't have fond memories of that whole process. And the fact that 4.2.4-atmel.1.1.3.avr32linux.1 is still the most current version of gcc doesn't make me very optimistic. So while Hans-Christian and others have been doing a great job of keeping AVR32 on life support, I tend to think that if there's not enough enthusiasm for the architecture to build a modern toolchain or add support for device tree, avr32-linux probably isn't going anywhere exciting. > A few weeks ago, I was telling Boris to let it not build for a while and > then remove it. You already went out of your way to make it work. Again, > feel free to send a patch removing avr32. I can only see a lot of > benefits for the Atmel ARM SoCs and the many cleanups that will follow. Agree, I can't help but feel that the AVR32 support is doing more harm than good at this point. > If nobody complains about the 4.10 breakage, You'll have plenty of time > to remove it for 4.12 I'm fine with that, but I haven't put much effort into keeping it alive lately. If Hans-Christian agrees, I'm willing to post a patch to remove it, or ack someone else's patch. Håvard