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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.02.1302191902470.18957@chino.kir.corp.google.com>
Date:	Tue, 19 Feb 2013 19:04:35 -0800 (PST)
From:	David Rientjes <rientjes@...gle.com>
To:	li guang <lig.fnst@...fujitsu.com>
cc:	linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org,
	x86@...nel.org, isimatu.yasuaki@...fujitsu.com
Subject: Re: [PATCH v4 1/4] acpi: move x86/mm/srat.c to
 x86/kernel/acpi/srat.c

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?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/