From: Zhu Yi <yi.zhu@intel•com>
To: Jeff Garzik <jeff@garzik•org>
Cc: "John W. Linville" <linville@tuxdriver•com>,
netdev@vger•kernel.org, linux-wireless@vger•kernel.org,
Andrew Morton <akpm@linux-foundation•org>
Subject: Re: Please pull 'upstream-jgarzik' branch of wireless-2.6
Date: Tue, 18 Dec 2007 09:24:49 +0800 [thread overview]
Message-ID: <1197941089.2857.252.camel@debian.sh.intel.com> (raw)
In-Reply-To: <476708EF.10403@garzik.org>
On Mon, 2007-12-17 at 18:40 -0500, Jeff Garzik wrote:
> drivers/net/wireless/iwlwifi/iwl3945-base.c: In function
> ‘iwl3945_alive_start’:
> drivers/net/wireless/iwlwifi/iwl3945-base.c:6285: error: implicit
> declaration of function ‘iwl_rate_control_unregister’
> make[4]: *** [drivers/net/wireless/iwlwifi/iwl3945-base.o] Error 1
> make[3]: *** [drivers/net/wireless/iwlwifi] Error 2
> make[2]: *** [drivers/net/wireless] Error 2
> make[1]: *** [drivers/net] Error 2
> make: *** [drivers] Error 2
We changed the namespace between 2.6.24 and upstream. So
iwl_rate_control_unregister should be renamed to
iwl3945_rate_control_unregister when the patch is merged from
fix-jgarzik to upstream-jgarzik. The same thing is also for
iwl4965_rate_control_unregister.
> I'll leave it there and assume that you will send a fix --on top of--
> netdev#upstream ...
I assume John will do it.
Thanks,
-yi
next prev parent reply other threads:[~2007-12-18 1:34 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-16 4:34 Please pull 'upstream-jgarzik' branch of wireless-2.6 John W. Linville
2007-12-17 23:24 ` Jeff Garzik
[not found] ` <47670514.4030204-o2qLIJkoznsdnm+yROfE0A@public.gmane.org>
2007-12-17 23:40 ` Jeff Garzik
2007-12-18 1:24 ` Zhu Yi [this message]
2007-12-18 2:25 ` iwlwifi: fix-up merge fall-out after namespace separation John W. Linville
[not found] ` <20071218022540.GB3640-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-12-18 3:04 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2008-01-08 22:23 Please pull 'upstream-jgarzik' branch of wireless-2.6 John W. Linville
2007-12-20 15:54 John W. Linville
2007-12-04 13:59 John W. Linville
2007-12-04 20:13 ` Jeff Garzik
2007-11-27 14:47 John W. Linville
[not found] ` <20071127144748.GA12408-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-12-04 13:55 ` John W. Linville
2007-11-06 1:16 John W. Linville
2007-11-06 17:43 ` Jeff Garzik
2007-09-15 13:21 John W. Linville
2007-09-18 1:54 ` Zhu Yi
[not found] <20070828231731.GB2967@tuxdriver.com>
[not found] ` <20070828231731.GB2967-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-08-31 13:44 ` Jeff Garzik
2007-08-15 0:36 John W. Linville
[not found] ` <20070815003637.GK7198-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-08-25 6:40 ` Jeff Garzik
2007-08-06 20:14 Please pull 'fixes-jgarzik' " John W. Linville
[not found] ` <20070806201441.GJ6442-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-08-06 20:16 ` Please pull 'upstream-jgarzik' " John W. Linville
2007-08-07 22:21 ` Jeff Garzik
2007-07-18 2:19 John W. Linville
[not found] ` <20070718021953.GC26907-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-07-18 22:31 ` Jeff Garzik
2007-07-10 18:57 John W. Linville
[not found] ` <20070710185758.GH7927-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-07-16 21:59 ` Jeff Garzik
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=1197941089.2857.252.camel@debian.sh.intel.com \
--to=yi.zhu@intel$(echo .)com \
--cc=akpm@linux-foundation$(echo .)org \
--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