Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757084Ab3EGJxC (ORCPT ); Tue, 7 May 2013 05:53:02 -0400 Received: from mga09.intel.com ([134.134.136.24]:17336 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756966Ab3EGJw7 (ORCPT ); Tue, 7 May 2013 05:52:59 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.87,627,1363158000"; d="scan'208";a="309468786" Date: Tue, 7 May 2013 11:52:38 +0200 From: Samuel Ortiz To: Haojian Zhuang Cc: Uwe =?iso-8859-1?Q?Kleine-K=F6nig?= , Robin Holt , Qing Xu , "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: How does commit 47ec340c not introduce a bug? Message-ID: <20130507095238.GA4387@zurbaran> References: <20130507091734.GM3658@sgi.com> <20130507092428.GK23285@pengutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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 Content-Length: 884 Lines: 29 On Tue, May 07, 2013 at 05:35:28PM +0800, Haojian Zhuang wrote: > > It's probably best to make this: > > > > static inline max8925_backlight_dt_init(struct platform_device *pdev, > > struct max8925_backlight_pdata *pdata) > > { > > return -ENODEV; > > } > > > > I've submitted this patch to fix this issue for a long time. > > Samuel, > > Should I send it again? To the backlight maintainers, yes. I carried 47ec340c as it was part of an MFD patchset, but now that it's upstream I shouldn't take any patches for it. Cheers, Samuel. -- Intel Open Source Technology Centre http://oss.intel.com/ -- 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/