On Thu, Jul 27, 2006 at 12:32:56PM -0600, Eric W. Biederman wrote: > > I have found a couple of moments and have been able to > catch up with most of the backlog of patches for kexec-tools. > There are several details I need to follow up on, and there is > some testing I want to do to make certain everything is working. > > The primary kexec-tools archive is: > git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/kexec-tools.git > > An archive to hold versions before 1.101 is at: > git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/kexec-tools-historic.git > > So far I have all version in there since 1.0 except 1.9, 1.92, and 1.93 > if someone happens to have a copy point me at it and I will update the > history. > > Patches that hang out in quilt for a while can be annoying to import > into git because their authorship information is not stored in an > unambiguous way. git is general is much stricter about the format > it's meta-data information is stored in. > > Maneesh in kdump10 there were two patches in particular that I have > not sorted out their who wrote them. If you could help me sort that > out I would appreciate it. > > ppc64-initrd-option.patch > ppc64-kdump-device_tree-sort.patch >
Both these patches are from Haren Myneni <[EMAIL PROTECTED]>. I do have the emails for these two patches but some how his email address didn't get captured and these were also not posted on fastboot mailing list. > Before I make a release here is my list of things I intend to look at: > - Why we have defined the location of the crash backup region twice. > - Why x86_64 arch_options is non-static. > - Why the ppc64 purgatory code has undefined symbols. > Until I can see what is going on there I believe support > any undefined symbols in purgatory is very much the wrong thing. > - The gcc 4.1.x warning fixes introduced a bunch of unnecessary casts > to squelch warnings. Casts totally disable the type system so > really weird things can happen if they live in the code base too > long. So I think I those casts need to be removed and another > solution found to shut up gcc. Probably I got the right persons on the cc-list to respond to these questions. Thanks Maneesh _______________________________________________ fastboot mailing list [email protected] https://lists.osdl.org/mailman/listinfo/fastboot
