On 21/02/2017 at 18:09:09 +0200, Andy Shevchenko wrote: > On Tue, Feb 21, 2017 at 1:27 PM, Alexandre Belloni > <alexandre.belloni@xxxxxxxxxxxxxxxxxx> wrote: > > (adding Hans-Christian) > > > > On 21/02/2017 at 13:02:21 +0200, Andy Shevchenko wrote: > >> Abusing platform data with pointers is also not welcome. > >> > >> > (in this case, avr32). > >> > >> It's dead de facto. > >> > >> When last time did you compile kernel for it? What was the version of kernel? > >> Did it get successfully? > >> > > > > v4.10-rc3 was building successfully but had some issues in the network > > code. > > Newer kernel doesn't link... > > >> When are we going to remove avr32 support from kernel completely? > > > Ask that to the avr32 maintainers. It still builds and is still booted > > by some people. And that actually seems to be you as you reported a bug > > we introduced in 4.3. I don't think we had any other report after that. > > https://patchwork.kernel.org/patch/9505727/ > > After that I gave up on it. Next time I will escalate directly to > Linus. It's a complete necrophilia. I spent already enough time to > look at that code. It brings now more burden than supports someone > somewhere. > As said, it builds fine without networking. Maybe the first step is to ask the avr32 maintainers. If you already did so, please feel free to send a patch to remove the whole architecture. The benefits for atmel will be: proper big endian support, removal of platform data from all the drivers, better clocksource handling. > > It can be frustrating at times to handle that platform but if it is > > working for someone, I don't see why we would remove it. > > How it's working if it's not linked? > Come on, v4.10 has just been release and v4.9 was building just fine. Do you really expect everybody to closely follow linux-next or update overnight? -- Alexandre Belloni, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
