From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from static-ip-62-75-166-246.inaddr.intergenia.de ([62.75.166.246]:44688 "EHLO vs166246.vserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758621AbXKGOjB (ORCPT ); Wed, 7 Nov 2007 09:39:01 -0500 From: Michael Buesch To: "John W. Linville" Subject: Re: Please pull 'fixes-davem' branch of wireless-2.6 Date: Wed, 7 Nov 2007 15:38:14 +0100 Cc: davem@davemloft.net, jeff@garzik.org, netdev@vger.kernel.org, linux-wireless@vger.kernel.org References: <20071107001314.GH4440@tuxdriver.com> In-Reply-To: <20071107001314.GH4440@tuxdriver.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Message-Id: <200711071538.14826.mb@bu3sch.de> (sfid-20071107_143907_930770_7519E4BC) Sender: linux-wireless-owner@vger.kernel.org List-ID: On Wednesday 07 November 2007 01:13:14 John W. Linville wrote: > "ssb: Fix initcall ordering" changes a subsys_initcall to an > fs_initcall. This seems like a bit of a hack, but it fixes a real > problem and I'm not sure what cleaner solution is either reasonable > or available. The comment in the patch explains the reasoning for this > somewhat unique situation. Well, ssb is not the only subsystem with this special requirement. Grep for fs_initcall. In my opinion we need another initcall to fix this issue. I think we need a post_subsys_initcall(). But that really is another issue that we can't decide in netdev. For now, this fix is harmless and fixes the bug. -- Greetings Michael.