Re: [PATCH v4 1/4] acpi: move x86/mm/srat.c tox86/kernel/acpi/srat.c

[li guang]

å 2013-02-19äç 19:04 -0800ïDavid Rientjesåéï
> On Wed, 20 Feb 2013, li guang wrote:
> 
> > > > No, it doesn't.  From next-20130219, you're missing at least two patches:
> > > > 
> > > > 3795e4893203 ("acpi, memory-hotplug: extend movablemem_map ranges to the end of node")
> > > > 9a561f4dfd70 ("acpi, memory-hotplug: support getting hotplug info from SRAT")
> > > > 
> > > > I'm trying to be patient in reviewing your patches, but please double 
> > > > check your work.
> > > 
> > > I have to say my latest pull has these commit, and can apply
> > > successfully.
> > > really don't know why you can't apply.
> 
> You should not be pulling linux-next, you should be fetching.
> > 
> > I mean although my patches did not based on latest linux-next(miss
> > several commits), but as I can see, they can be applied to latest
> > linux-next (tag next-20130218) successfully.
> > 
> 
> next-20130218 is not the latest linux-next as I've already said.  Do this: 
> go to 
> http://git.kernel.org/?p=linux/kernel/git/next/linux-next-history.git;a=blob_plain;f=arch/x86/mm/srat.c;hb=HEAD 
> and search for handle_movablemem().  That's one of the functions added in 
> one of the commits I mentioned and was from February.  Now search your 
> patch for handle_movablemem().  See a problem?

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.



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/