Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752480Ab1CPLwc (ORCPT ); Wed, 16 Mar 2011 07:52:32 -0400 Received: from smtp.nokia.com ([147.243.128.24]:49762 "EHLO mgw-da01.nokia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751290Ab1CPLw0 (ORCPT ); Wed, 16 Mar 2011 07:52:26 -0400 Subject: Re: linux-next: build failure after merge of the final tree (ubi tree related) From: Artem Bityutskiy Reply-To: Artem.Bityutskiy@nokia.com To: Stephen Rothwell Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Benjamin Herrenschmidt , Paul Mackerras , linuxppc-dev@lists.ozlabs.org In-Reply-To: <20110316175041.67c4f371.sfr@canb.auug.org.au> References: <20110316175041.67c4f371.sfr@canb.auug.org.au> Content-Type: text/plain; charset="UTF-8" Organization: Nokia Date: Wed, 16 Mar 2011 13:48:39 +0200 Message-ID: <1300276119.2817.9.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 (2.32.1-1.fc14) Content-Transfer-Encoding: 8bit X-Nokia-AV: Clean Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 967 Lines: 24 On Wed, 2011-03-16 at 17:50 +1100, Stephen Rothwell wrote: > After merging the final tree, today's linux-next build (powerpc > allyesconfig) failed like this: > > drivers/mtd/ubi/io.c: In function 'ubi_dbg_check_write': > drivers/mtd/ubi/io.c:1348: error: 'PAGE_KERNEL' undeclared (first use in this function) > drivers/mtd/ubi/io.c: In function 'ubi_dbg_check_all_ff': > drivers/mtd/ubi/io.c:1412: error: 'PAGE_KERNEL' undeclared (first use in this function) > > Caused by commit 823ed5091113 ("UBI: allocate write checking buffer on demand"). > > I don't know how to fix this, so I have left it for today. Fixed, sorry for the hassle and thank you! -- Best Regards, Artem Bityutskiy (Артём Битюцкий) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/