linux-kernel - Re: linux-next: build failure after merge of the akpm tree

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: <20120105231958.GA15643@kroah.com>
Date:	Thu, 5 Jan 2012 15:19:58 -0800
From:	Greg KH <greg@...ah.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Kay Sievers <kay.sievers@...y.org>,
	Michael Holzheu <holzheu@...ux.vnet.ibm.com>
Subject: Re: linux-next: build failure after merge of the akpm tree

On Thu, Jan 05, 2012 at 06:29:37PM +1100, Stephen Rothwell wrote:
> Hi Andrew,
> 
> After merging the akpm tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
> 
> drivers/base/memory.c: In function 'memory_block_change_state':
> drivers/base/memory.c:306:22: error: 'struct memory_block' has no member named 'sysdev'
> drivers/base/memory.c:309:22: error: 'struct memory_block' has no member named 'sysdev'
> 
> Caused by commit 2691cc121386 ("kdump: add udev events for memory
> online/offline") interacting with commit 10fbcf4c6cb1 ("convert 'memory'
> sysdev_class to a regular subsystem") from the driver-core tree.

I can't recall this kdump patch coming through before, have I seen it?
creating new uevents is not something to be done lightly, has this been
tested with the existing userspace tools to make sure it doesn't cause
problems?

thanks,

greg k-h
--
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/