From: Larry Finger <larry.finger@lwfinger.net>
To: Patrick McHardy <kaber@trash.net>
Cc: Jiri Benc <jbenc@suse.cz>,
Bcm43xx-dev@lists.berlios.de, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] mac80211: Fix for missing global (tcf_destroy_chain) in build
Date: Wed, 02 May 2007 10:21:48 -0500 [thread overview]
Message-ID: <4638AC8C.9060706@lwfinger.net> (raw)
In-Reply-To: <4638A163.8030505@trash.net>
Patrick McHardy wrote:
>
>
> That pretty much defeats the reason why CONFIG_NET_SCH_FIFO was created.
> So far without CONFIG_NET_SCHED the wme scheduler didn't even register,
> so it seems the proper fix is to get rid of all #ifdef CONFIG_NET_SCHED
> and simply avoid building it.
At least this "fix" lets the system build. Whomever broke it needs to do the proper fix.
Larry
prev parent reply other threads:[~2007-05-02 15:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-02 14:22 [PATCH] mac80211: Fix for missing global (tcf_destroy_chain) in build Larry Finger
2007-05-02 14:34 ` Patrick McHardy
2007-05-02 15:21 ` Larry Finger [this message]
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=4638AC8C.9060706@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=Bcm43xx-dev@lists.berlios.de \
--cc=jbenc@suse.cz \
--cc=kaber@trash.net \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).