From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935044AbcCJE4P (ORCPT ); Wed, 9 Mar 2016 23:56:15 -0500 Received: from mail-pa0-f44.google.com ([209.85.220.44]:36293 "EHLO mail-pa0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753658AbcCJE4N (ORCPT ); Wed, 9 Mar 2016 23:56:13 -0500 Message-ID: <56E0FE58.8070503@gmail.com> Date: Thu, 10 Mar 2016 10:25:52 +0530 From: Sudip Mukherjee User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: =?UTF-8?B?TcOlbnMgUnVsbGfDpXJk?= , Andy Shevchenko CC: Guenter Roeck , Hans-Christian Noren Egtvedt , Haavard Skinnemoen , "linux-kernel@vger.kernel.org" Subject: Re: avr32 build failures in linux-next References: <56B4C799.5070401@roeck-us.net> <56B4CE8C.8040307@gmail.com> <20160206115722.GA32647@samfundet.no> <56B61D21.2010407@roeck-us.net> <56B964D9.8000300@roeck-us.net> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thursday 10 March 2016 01:20 AM, Måns Rullgård wrote: > Andy Shevchenko writes: > >> On Tue, Feb 9, 2016 at 6:02 AM, Guenter Roeck wrote: >>> On 02/08/2016 08:06 AM, Andy Shevchenko wrote: >>>> >>>> On Sat, Feb 6, 2016 at 7:28 PM, Måns Rullgård wrote: >>>> >>>>> Not very surprising either. The number of people using Linux on avr32 >>>>> is probably approximately zero, and if anyone is, they're likely still >>>>> running 2.6.32 or thereabouts. >>>> >>>> >>>> Once I tried up the topic about removal avr32 for good, but looks like >>>> it wasn't a good time. Maybe now is better? It would really reduce a >>>> burden on many drivers. >>>> >>> I would agree, as long as the maintainers agree. We don't want to repeat >>> the h8300 experience. >> >> So, are we going to agree that avr32 must be retired from next cycle? >> >> P.S. I have no idea how to fix this "…relocation truncated to fit: >> R_AVR32_21S…", though I can test anything anyone propose. > > I'd like to try fixing it before we delete anything. At the very least, > it's always a good idea to figure out exactly why it broke, just to be > sure it isn't a broader issue that has yet to manifest itself elsewhere. > I will suggest keeping it for one more cycle and see if it can be fixed. regards sudip