Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752442Ab0K3XuE (ORCPT ); Tue, 30 Nov 2010 18:50:04 -0500 Received: from kroah.org ([198.145.64.141]:42976 "EHLO coco.kroah.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751640Ab0K3XuD (ORCPT ); Tue, 30 Nov 2010 18:50:03 -0500 Date: Tue, 30 Nov 2010 15:49:37 -0800 From: Greg KH To: Russell King - ARM Linux Cc: Arnd Bergmann , Linus Walleij , Jimmy RUBIN , Dan JOHANSSON , Marcus LORENTZON , Linux Kernel Mailing List , dri-devel@lists.freedesktop.org, "linux-arm-kernel@lists.infradead.org" , "linux-media@vger.kernel.org" Subject: Re: [PATCH 09/10] MCDE: Add build files and bus Message-ID: <20101130234937.GA7156@kroah.com> References: <201011261224.59490.arnd@arndb.de> <201011301621.48140.arnd@arndb.de> <20101130184049.GC8521@n2100.arm.linux.org.uk> <20101130184834.GA16055@kroah.com> <20101130220550.GD8521@n2100.arm.linux.org.uk> <20101130230533.GA11342@kroah.com> <20101130234215.GE8521@n2100.arm.linux.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20101130234215.GE8521@n2100.arm.linux.org.uk> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1493 Lines: 34 On Tue, Nov 30, 2010 at 11:42:15PM +0000, Russell King - ARM Linux wrote: > > It's a work in progress, but wherever possible, I encourage people to > > not make 'struct device' static. > > Right, so saying to ARM developers that they can't submit code which > adds new static device structures is rather problematical then, and > effectively brings a section of kernel development to a complete > standstill - it means no support for additional ARM platforms until > this issue is resolved. (This "condition" was mentioned by Arnd > earlier in this thread, and was put in such a way that it was now > a hard and fast rule.) Sorry, I didn't mean for that to be mentioned that way at all, as I know the issues that are keeping this from happening. > I feel it would be better to allow the current situation to continue. > If we start telling people that they can't use statically declared > devices without first having an alternative, we'll end up with people > inventing their own individual - and different - solutions to this > problem, which could actually make the problem harder to resolve in > the longer term. Ok, but again, I do encourage, wherever possible, that people do not statically create a 'struct device'. thanks, greg k-h -- 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/