From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752826AbcBLSxv (ORCPT ); Fri, 12 Feb 2016 13:53:51 -0500 Received: from mail-pa0-f67.google.com ([209.85.220.67]:36044 "EHLO mail-pa0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752442AbcBLSxu (ORCPT ); Fri, 12 Feb 2016 13:53:50 -0500 Date: Fri, 12 Feb 2016 10:53:47 -0800 From: Brian Norris To: Simon Arlott , Ralf Baechle Cc: David Woodhouse , Kevin Cernekee , Florian Fainelli , Jonas Gorski , Linux Kernel Mailing List , MIPS Mailing List , MTD Maling List , sfr@canb.auug.org.au Subject: Re: [PATCH linux-next v4 07/11] MIPS: bcm63xx: nvram: Remove unused bcm63xx_nvram_get_psi_size() function Message-ID: <20160212185347.GA21465@google.com> References: <566DF43B.5010400@simon.arlott.org.uk> <566DF625.3060801@simon.arlott.org.uk> <20160126191607.GA111152@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160126191607.GA111152@google.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Ralf, On Tue, Jan 26, 2016 at 11:16:07AM -0800, Brian Norris wrote: > On Sun, Dec 13, 2015 at 10:50:13PM +0000, Simon Arlott wrote: > > Remove bcm63xx_nvram_get_psi_size() as it now has no users. > > > > Signed-off-by: Simon Arlott > > --- > > v4: New patch. > > Ralf, > > Please revert this and send it to Linus (or else, I can send it myself). > This is causing build failures, because I didn't take the rest of > Simon's series yet. > > drivers/mtd/bcm63xxpart.c: In function 'bcm63xx_parse_cfe_partitions': > drivers/mtd/bcm63xxpart.c:93:2: error: implicit declaration of function 'bcm63xx_nvram_get_psi_size' [-Werror=implicit-function-declaration] > > I will reply to the series if/when I accept any patches from it. I would > appreciate it if you would do the same. I see that the revert made it to Linus. Thanks! I've now pushed the dependent pieces to l2-mtd.git, and they should make it to v4.6-rc1. So I guess it's fair game to re-apply this patch? Although, if you don't merge in my MTD branch first, you'd still be breaking bisectability... Maybe it's a post-rc1 candidate? Brian