mcgrof@xxxxxxxxxx,acme@xxxxxxxxxx,tglx@xxxxxxxxxxxxx,mingo@xxxxxxxxxx,jpoimboe@xxxxxxxxxx,bp@xxxxxxxxx,linux@xxxxxxxxxxxxxxxx,mhiramat@xxxxxxxxxx,masami.hiramatsu.pt@xxxxxxxxxxx,jbaron@xxxxxxxxxx,heiko.carstens@xxxxxxxxxx,ananth@xxxxxxxxxxxxxxxxxx,anil.s.keshavamurthy@xxxxxxxxx,davem@xxxxxxxxxxxxx,realmz6@xxxxxxxxx,x86@xxxxxxxxxx,luto@xxxxxxxxxxxxxx,keescook@xxxxxxxxxxxx,torvalds@xxxxxxxxxxxxxxxxxxxx,gregkh@xxxxxxxxxxxxxxxxxxx,rusty@xxxxxxxxxxxxxxx,gnomes@xxxxxxxxxxxxxxxxxxx,alan@xxxxxxxxxxxxxxx,dwmw2@xxxxxxxxxxxxx,arnd@xxxxxxxx,ming.lei@xxxxxxxxxxxxx,linux-arch@xxxxxxxxxxxxxxx,benh@xxxxxxxxxxxxxxxxxxx,ananth@xxxxxxxxxx,pebolle@xxxxxxxxxx,fontana@xxxxxxxxxxxxxxx,david.vrabel@xxxxxxxxxx,konrad.wilk@xxxxxxxxxx,mcb30@xxxxxxxx,jgross@xxxxxxxx,andrew.cooper3@xxxxxxxxxx,andriy.shevchenko@xxxxxxxxxxxxxxx,paul.gortmaker@xxxxxxxxxxxxx,xen-devel@xxxxxxxxxxxxxxxxxxx,ak@xxxxxxxxxxxxxxx,pali.rohar@xxxxxxxxx,dvhart@xxxxxxxxxxxxx,platform-driver-x86@xxxxxxxxxxxxxxx,mmarek@xxxxxxxx,linux@ra! smusville moes.dk,jkosina@xxxxxxx,korea.drzix@xxxxxxxxx,linux-kbuild@xxxxxxxxxxxxxxx,tony.luck@xxxxxxxxx,akpm@xxxxxxxxxxxxxxxxxxxx,linux-ia64@xxxxxxxxxxxxxxx,linux-arm-kernel@xxxxxxxxxxxxxxxxxxx,linux-sh@xxxxxxxxxxxxxxx,sparclinux@xxxxxxxxxxxxxxx,catalin.marinas@xxxxxxx,will.deacon@xxxxxxx,rostedt@xxxxxxxxxxx,jani.nikula@xxxxxxxxx,mchehab@xxxxxxxxxxxxxxx,markus.heiser@xxxxxxxxxxx,jolsa@xxxxxxxxxx,msalter@xxxxxxxxxx,chris@xxxxxxxxxx,jcmvbkbc@xxxxxxxxx,linux-xtensa@xxxxxxxxxxxxxxxx,paulus@xxxxxxxxx,mpe@xxxxxxxxxxxxxx,James.Bottomley@xxxxxxxxxxxxxxxxxxxxx Message-ID: <5150EFE4-3E00-4BD2-AE6F-F99FBBC74273@xxxxxxxxx> On August 20, 2016 9:59:59 PM PDT, Rich Felker <dalias@xxxxxxxx> wrote: >On Fri, Aug 19, 2016 at 11:57:18PM -0500, Rob Landley wrote: >> On 08/19/2016 04:41 PM, mcgrof@xxxxxxxxxx wrote: >> > Please let me know if there are any issue or questions. >> >> Only that this has been the majority of the traffic on the linux-sh >> mailing list for over a month and I'm still not sure why anyone >should care. >> >> I have no idea what problem it solves, despite reading a couple dozen >> messages in the thread, and the most recent two 0/x intro messages. >Its >> purpose seems to be ensuring that lld.llvm.org has more work to do if >it >> ever wants to build the kernel without binutils? >> >> I also am not certain why every revision of it is cc'd to linux-sh. >Is >> it generic linker infrastructure change, or is it something that >affects >> this architecture specifically? As far as I can tell nothing in this >> most recent 7-patch series touches arch/sh at all, you just cc'd our >> list because you think the work you're doing is _important_, not that >> it's specifically relevant to us. > >Incidentally I'm happy to have been CC'd since this infrastructure is >_really_ nice for doing things generically with device tree. The >ability to add new linker-section-based tables without having to >manually hack up linker script templates will make it so we can do >things like adding tables for cache controllers or mmus (that are >needed quite early in init and can't go through the platform device >system). > >BTW we kinda lucked out that there was already the linker table >infrastructure for cpu enable methods for smp; this patch series makes >it so future stuff doesn't have to rely on luck or invasive changes. > >Rich Incidentally, I want to use this for the RAID algorithms. -- Sent from my Android device with K-9 Mail. Please excuse brevity and formatting. -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
