Re: avr32 build failures in linux-next

From: Andy Shevchenko
Date: Thu Mar 10 2016 - 08:53:59 EST

On Thu, Mar 10, 2016 at 3:38 PM, MÃns RullgÃrd <mans@xxxxxxxxx> wrote:
> Andy Shevchenko <andy.shevchenko@xxxxxxxxx> writes:
>> On Tue, Feb 9, 2016 at 6:02 AM, Guenter Roeck <linux@xxxxxxxxxxxx> wrote:
>>> On 02/08/2016 08:06 AM, Andy Shevchenko wrote:
>>>> On Sat, Feb 6, 2016 at 7:28 PM, MÃns RullgÃrd <mans@xxxxxxxxx> 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?
Anyway confirm that after disabling that kernel builds as usual.

With Best Regards,
Andy Shevchenko