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 for Android: free password hash cracker in your pocket

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

Message-ID: <alpine.DEB.2.02.1302191802490.14999@chino.kir.corp.google.com>
Date:	Tue, 19 Feb 2013 18:08:02 -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:

> > > This doesn't apply to Linus' tree nor does it apply to linux-next.  Which 
> > > tree are you basing this on?
> > 
> > I did based on linux-next, 
> > but it seems without commit 479a99a8e510c8839e0d3d3de8391f8bc61b9760
> > which you may want to see.
> > let me see why it missed.
> 
> I pulled latest for linux-next
> and can apply my patches smoothly.
> 

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.
--
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/