Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751987AbcCJOY7 (ORCPT ); Thu, 10 Mar 2016 09:24:59 -0500 Received: from unicorn.mansr.com ([81.2.72.234]:55556 "EHLO unicorn.mansr.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751775AbcCJOYv (ORCPT ); Thu, 10 Mar 2016 09:24:51 -0500 From: =?iso-8859-1?Q?M=E5ns_Rullg=E5rd?= To: Andy Shevchenko Cc: Guenter Roeck , Hans-Christian Noren Egtvedt , Sudip Mukherjee , 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> Date: Thu, 10 Mar 2016 14:24:49 +0000 In-Reply-To: (Andy Shevchenko's message of "Thu, 10 Mar 2016 15:53:49 +0200") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1406 Lines: 36 Andy Shevchenko writes: > On Thu, Mar 10, 2016 at 3:38 PM, 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. >> >> The error goes away if CONFIG_AIO_THREAD is disabled. Still don't know why. > > A straight guess: it has reduced enough room to fit the relocation window? That was my first guess as well, but it was wrong. See the patch I just sent for an explanation. -- Måns Rullgård