From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: "Måns Rullgård" <mans@mansr.com>,
"Andy Shevchenko" <andy.shevchenko@gmail.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
Hans-Christian Noren Egtvedt <egtvedt@samfundet.no>,
Haavard Skinnemoen <hskinnemoen@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: avr32 build failures in linux-next
Date: Thu, 10 Mar 2016 10:25:52 +0530 [thread overview]
Message-ID: <56E0FE58.8070503@gmail.com> (raw)
In-Reply-To: <yw1xvb4v4ej1.fsf@unicorn.mansr.com>
On Thursday 10 March 2016 01:20 AM, Måns Rullgård wrote:
> Andy Shevchenko <andy.shevchenko@gmail.com> writes:
>
>> On Tue, Feb 9, 2016 at 6:02 AM, Guenter Roeck <linux@roeck-us.net> 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@mansr.com> 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
next prev parent reply other threads:[~2016-03-10 4:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-05 16:02 avr32 build failures in linux-next Guenter Roeck
2016-02-05 16:32 ` Sudip Mukherjee
2016-02-06 11:57 ` Hans-Christian Noren Egtvedt
2016-02-06 14:01 ` Måns Rullgård
2016-02-06 16:19 ` Guenter Roeck
2016-02-06 17:28 ` Måns Rullgård
2016-02-08 16:06 ` Andy Shevchenko
2016-02-09 4:02 ` Guenter Roeck
2016-03-09 19:30 ` Andy Shevchenko
2016-03-09 19:50 ` Måns Rullgård
2016-03-10 4:55 ` Sudip Mukherjee [this message]
2016-03-10 13:38 ` Måns Rullgård
2016-03-10 13:53 ` Andy Shevchenko
2016-03-10 14:24 ` Måns Rullgård
2016-03-10 14:29 ` One Thousand Gnomes
2016-03-10 14:31 ` Måns Rullgård
2016-03-10 15:10 ` Andy Shevchenko
2016-02-06 15:50 ` Guenter Roeck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56E0FE58.8070503@gmail.com \
--to=sudipm.mukherjee@gmail.com \
--cc=andy.shevchenko@gmail.com \
--cc=egtvedt@samfundet.no \
--cc=hskinnemoen@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mans@mansr.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.