> -----Original Message----- > From: Luck, Tony > Sent: 2006年9月21日 0:43 > To: Horms; Zou, Nanhai > Cc: Linux-IA64; fastboot > Subject: RE: [Patch] IA64 Kexec/Kdump patch for 2.6.18-rc6 > > > Tony, Nan Hai, do you have any thoughts on merging this > > series into ia64 test? Its really far to big to be managed > > as a single unit. I would be much more comfortable if > > we could track small incremental changes. Even the diff > > between the current and previous version (as below) is quite large. > > I'm open to suggestions. My current inclination is to abandon the > existing kexec/kdump patches that are currently in my test tree[1] and > replace them with the latest set of patches. So a re-diff of all that > is considered good against 2.6.18 would be ideal for that. > > Breaking the patch into some smaller pieces would also be good, > but I don't think this needs to be taken to extremes (just define > a few basic areas and split the patch ... I don't thing it is > worth spending days/weeks to split this into a sequence of 37 individually > crafted patches, with the kernel being fully functional at every > one of the 36 intermediate points). > > -Tony > > [1] My test tree is not a guaranteed monotonic increasing sequence of > changesets. I've already blown it away once before to clean out all > the crufty "Auto-update from upstream" commits that my workflow generates. > It's due for another clean-up anyway. I put those in a big patch to help people testing the IA64 kdump. People can grab a base kernel and the patch to test. Thanks Zou Nan hai - To unsubscribe from this list: send the line "unsubscribe linux-ia64" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
![]() |