From: Michael Buesch <mb@bu3sch•de>
To: "John W. Linville" <linville@tuxdriver•com>
Cc: davem@davemloft•net, jeff@garzik•org, netdev@vger•kernel.org,
linux-wireless@vger•kernel.org
Subject: Re: Please pull 'fixes-davem' branch of wireless-2.6
Date: Wed, 7 Nov 2007 15:38:14 +0100 [thread overview]
Message-ID: <200711071538.14826.mb@bu3sch.de> (raw)
In-Reply-To: <20071107001314.GH4440@tuxdriver.com>
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.
next prev parent reply other threads:[~2007-11-07 14:39 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 0:13 Please pull 'fixes-davem' branch of wireless-2.6 John W. Linville
2007-11-07 14:38 ` Michael Buesch [this message]
[not found] ` <20071107001314.GH4440-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-11-07 18:51 ` John W. Linville
2007-11-08 0:32 ` David Miller
[not found] ` <20071107.163200.25509588.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2007-11-08 2:11 ` Please pull 'fixes-davem' branch of wireless-2.6 (this time for real!) John W. Linville
[not found] ` <20071108021119.GD11957-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-11-11 6:02 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2008-01-16 21:26 Please pull 'fixes-davem' branch of wireless-2.6 John W. Linville
[not found] ` <20080116212645.GD3164-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2008-01-18 12:33 ` David Miller
2008-01-08 5:14 John W. Linville
[not found] ` <20080108051425.GA3125-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2008-01-08 5:21 ` David Miller
2007-12-20 15:52 John W. Linville
[not found] ` <20071220155227.GE3139-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-12-25 6:07 ` David Miller
2007-12-17 20:54 John W. Linville
2007-12-18 6:56 ` David Miller
2007-11-30 3:31 John W. Linville
2007-11-30 12:34 ` Herbert Xu
2007-11-20 22:10 John W. Linville
[not found] ` <20071120221025.GH16090-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-11-21 1:25 ` David Miller
2007-11-15 2:51 John W. Linville
2007-11-15 3:40 ` David Miller
2007-10-26 3:10 John W. Linville
2007-10-26 4:11 ` John W. Linville
2007-10-18 22:08 John W. Linville
[not found] ` <20071018220859.GG8510-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-10-19 4:57 ` David Miller
2007-10-17 2:31 John W. Linville
[not found] ` <20071017023145.GA2848-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-10-17 3:29 ` Michael Wu
2007-10-17 14:53 ` John W. Linville
2007-09-15 13:15 John W. Linville
2007-08-15 0:32 John W. Linville
[not found] ` <20070815003234.GI7198-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-08-15 1:33 ` David Miller
2007-08-06 20:13 John W. Linville
2007-08-08 1:08 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200711071538.14826.mb@bu3sch.de \
--to=mb@bu3sch$(echo .)de \
--cc=davem@davemloft$(echo .)net \
--cc=jeff@garzik$(echo .)org \
--cc=linux-wireless@vger$(echo .)kernel.org \
--cc=linville@tuxdriver$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox