From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755569Ab3CUAKw (ORCPT ); Wed, 20 Mar 2013 20:10:52 -0400 Received: from mail-pb0-f44.google.com ([209.85.160.44]:65081 "EHLO mail-pb0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754545Ab3CUAKc (ORCPT ); Wed, 20 Mar 2013 20:10:32 -0400 Date: Wed, 20 Mar 2013 17:10:30 -0700 (PDT) From: David Rientjes X-X-Sender: rientjes@chino.kir.corp.google.com To: Randy Dunlap , HATAYAMA Daisuke cc: Stephen Rothwell , Andrew Morton , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, kexec@lists.infradead.org Subject: Re: linux-next: Tree for Mar 20 (vmcore) In-Reply-To: Message-ID: References: <20130320160536.54e62fc11a3651494b710e3b@canb.auug.org.au> <5149E813.8060307@infradead.org> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 20 Mar 2013, David Rientjes wrote: > I don't think that's it, linux/kexec.h already gets included indirectly. > The problem is that CONFIG_KEXEC isn't set so the definition in kexec.h is > meaningless. > > This comes from "vmcore: check NT_VMCORE_PAD as a mark indicating the end > of ELF note buffer" merged through the -mm tree. I've added the patch's > author and Andrew to the cc. > > How can this be protected by CONFIG_KEXEC? > These patches were removed from -mm today so it should no longer be a problem. If the patchset is reintroduced, please keep this build failure in the back of your mind, thanks.