On Wed, 20 Feb 2013, li guang wrote: > Yes, I know there's no new changes in my patch as I said before(not > based on lasted), but as I try to apply my patch(1/4), it will do > the right work to move current srat.c from arch/x86/mm/ to > arch/x86/kernel/acpi/ regardless of what I based is not latest. > Sorry, but that makes no sense. Your patch cannot be used cleanly if there have been subsequent changes to a hunk prior to applying it -- in this case the hunk would be the entire file since you're removing it. These patches would also be pushed by the x86 maintainers, who are not cc'd on this patch, and I think it would be unfair to ask them to make up for your inability to generate a bleeding edge patch with linux-next. The changes already cited in this thread have been in linux-next for almost two weeks, yet you refuse to rebase on top of them. -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
